New to using MySQL....

[CTho9305]

Originally posted by: n0cmonkey

Originally posted by: Zugzwang152

Originally posted by: n0cmonkey

Originally posted by: Zugzwang152

Originally posted by: Armitage

Originally posted by: kamper
Now that this thread is wrapped up I'm going to totally nef on it and say that postgres sequences > mysql autoincrement 😉

Why?

because its the new software/apps forum fad to diss mysql apparently. 😛

The MySQL vs. PostgreSQL fight has been going on for a while. If it's happening here, we're finally catching up to the rest of the internet.

They both have pros and cons.

only in the last week or so i've noticed that every mysql thread seems to have someone come in and crap on it by saying how much it sucks.

Then AT's several YEARS behind. 😛

:beer:

I started on Microsoft SQL server (I learned SQL on the job) and was really pleased. I learned good practices (for example, using stored procs for all accesses to make it possible to change the underlying schema without breaking apps, and secure design - making sure that apps can't access tables directly but can only call stored procedures which you know do accesses safely, etc). When I installed MySQL on my machine, I was highly disappointed, because it really sucks. The fact that it's improving doens't mean it's not still very inferior to real RDBMSes. AIUI, it still doens't do transactions properly.

For years the mysql people claimed these features weren't needed, but now they go and slowly implement them? Great attitude :rolleyes;.

 

[Armitage]

Originally posted by: CTho9305

Originally posted by: n0cmonkey

Originally posted by: Zugzwang152

Originally posted by: n0cmonkey

Originally posted by: Zugzwang152

Originally posted by: Armitage

Originally posted by: kamper
Now that this thread is wrapped up I'm going to totally nef on it and say that postgres sequences > mysql autoincrement 😉

Why?

because its the new software/apps forum fad to diss mysql apparently. 😛

The MySQL vs. PostgreSQL fight has been going on for a while. If it's happening here, we're finally catching up to the rest of the internet.

They both have pros and cons.

only in the last week or so i've noticed that every mysql thread seems to have someone come in and crap on it by saying how much it sucks.

Then AT's several YEARS behind. 😛

:beer:

I started on Microsoft SQL server (I learned SQL on the job) and was really pleased. I learned good practices (for example, using stored procs for all accesses to make it possible to change the underlying schema without breaking apps, and secure design - making sure that apps can't access tables directly but can only call stored procedures which you know do accesses safely, etc). When I installed MySQL on my machine, I was highly disappointed, because it really sucks. The fact that it's improving doens't mean it's not still very inferior to real RDBMSes. AIUI, it still doens't do transactions properly.

For years the mysql people claimed these features weren't needed, but now they go and slowly implement them? Great attitude :rolleyes;.

Just because these features aren't needed to have a useful tool doesn't mean that the features are useless and the tool wouldn't be better with them. :roll:

My car doesn't *need* air conditioning. It'd still do its job fine without it. But it sure is nice to have. Now if I lived in Phoenix, I might argue that AC is essential and a car without AC is not suitable for that environment - just like for some tasks MySQL is obviosly not a reasonable choice.

I'm not willing to pay for Oracle and MS isn't an option. I tried Postgres and didn't like it. MySQL has done exceptionally well for what I'm using it for - if it's not a "real" RDBMS, so be it.

 

[kamper]

Originally posted by: CTho9305
:beer:

I started on Microsoft SQL server (I learned SQL on the job) and was really pleased. I learned good practices (for example, using stored procs for all accesses to make it possible to change the underlying schema without breaking apps, and secure design - making sure that apps can't access tables directly but can only call stored procedures which you know do accesses safely, etc). When I installed MySQL on my machine, I was highly disappointed, because it really sucks. The fact that it's improving doens't mean it's not still very inferior to real RDBMSes. AIUI, it still doens't do transactions properly.

For years the mysql people claimed these features weren't needed, but now they go and slowly implement them? Great attitude :rolleyes;.

Two issues with the above.
First, using all stored procs may protect your app from schema changes but it also does a fine job of ensuring that you'll have a tough time if you ever want to deploy on a different database. Your application can easily have a layer where you keep all db access and, hence, all schema changes. Better yet, using an abstraction tool (like Hibernate if you're using java) makes databases almost plug and play and schema changes as simple as the real effect that they have on your data.

Second, I agree with Armitage. Of course mysql isn't SQL Server but it doesn't need to be because it's still very useful to a lot of people. To continue his car analogy, call sql server a porsche and call mysql a corolla or something. To say that people shouldn't drive corollas because porsches can be had is silly. Especially if you factor in that the corolla is free and you can't drive the porsche on non-microsoft highways 😛

 

[CTho9305]

First, using all stored procs may protect your app from schema changes but it also does a fine job of ensuring that you'll have a tough time if you ever want to deploy on a different database.

If you're using server-specific SQL in the app, you'll have to fix it anyway. Switching RDBMSes is rarely fun.

Your application can easily have a layer where you keep all db access and, hence, all schema changes.

Sure, but you still have to fix *every* client app.

To say that people shouldn't drive corollas because porsches can be had is silly.

You can drive the corolla, just don't claim it's as good as the porsche, or useful in a race.

 

[kamper]

Originally posted by: CTho9305

To say that people shouldn't drive corollas because porsches can be had is silly.

You can drive the corolla, just don't claim it's as good as the porsche, or useful in a race.

Ignore my whole development style rant. It was kinda pointless 🙂

Nobody's claiming that a corolla is better in a race than a porsche. People are saying it's a better car to drive to work every day (which it is) but it seems like others are critical of the idea that anybody would want to drive it at all.

 

[n0cmonkey]

I don't like MySQL's threading style. PostgreSQL works better on less thread capable systems.