Save yourself and forget MySQL and MariaDB

[zzzato]

This means you can lose data without knowing it is happening.

This is my big concern with MySQL and SQLite. They seem to have their own [warped] ideas or interpretation of the table schema rules. The result is invalid (as far as I'm concerned) or modified data - without the application/developer/end-user being notified of this. So what you put in, is not what you get out. When it comes to data - that is a huge concern to me.

I used Ibm2 (win e As/400), M$SqlServer (CE too....), Msde, Sybase, Oracle, Firebird, Interbase.
Now I'm using MySql too and I've some question about it...

1) WHY default server mode IS NOT strict mode?
2) WHY mysqldump doens't have a dump default filename?
3) WHY mysqldump has a default to NOT export stored procedures?

In other word, WHY MySql is different?

About strict mode, MySqwl has different engines. So, it IS NOT like other databases.
I'm using InnoDb engine. MAYBE, using MyIsam strict mode is not a critical behavoir...
About other questions, I'm searching a VALID answer.

A friend of mine says me "Mysql was not born in windows....you can get mysqldump output to do fantastic things using bash!".
But...  Oracle was not born in windows too..and exp dumps stored procedures and HAS a default file name for dump...

Cher.

A.

[goodname]

MySQL is different because it was targeted at building web pages. On a web site the last thing you want visitors to see is a database error page. If some user writes a post longer then 255 characters it didn't matter that the string was truncated. The web site kept running. The behaviour has had to adapt as the target audience has changed.

SQLite is targeted at embedded data storage. Do not have a lot of experience with this engine but I'm sure there are good target user reasons for it's behaviour. It is arguably the most widely distributed and used database engine in the world so what it does it does very well.

Oracle, Firebird, MSSQL, PostgreSQL were all designed for client server environments where the data integrity was the most important priority.

[zzzato]

MySQL is different because it was targeted at building web pages. On a web site the last thing you want visitors to see is a database error page. If some user writes a post longer then 255 characters it didn't matter that the string was truncated. The web site kept running. The behaviour has had to adapt as the target audience has changed.

SQLite is targeted at embedded data storage. Do not have a lot of experience with this engine but I'm sure there are good target user reasons for it's behaviour. It is arguably the most widely distributed and used database engine in the world so what it does it does very well.

Oracle, Firebird, MSSQL, PostgreSQL were all designed for client server environments where the data integrity was the most important priority.

Hi. Thanks for your answer.
I agree about different target and/or strict mode.
But what do you think about my mysqldump  questions?
Why it has not a lot of default  values?

Cher.

A.