On 12/22/08 5:37 PM, Jim Starkey wrote:
Databases are not supposed to drop data and operations on the floor. It is permissible to continue after an operation is a suitable log is kept of failures so can application can tell what actually happened and what did not. A machine readable log, however, is non-trivial to design and implement. A temporary table with a semi-magic name, maybe? But letting unknown stuff disappear through the cracks is just no good.
Well, this is where ideology comes in to play. It is an opinion that this is what databases are supposed to do. Ignoring the fact that the developer has to tell the database to IGNORE the errors, it is my belief that a database or any other software I choose to use are there to be used as I see fit for my needs.
The good news is that we have a group that can decide what is best. I would imagine that DBMS designed by you and one by me would be quite different and might be quite difficult for the general public to use in both cases. However, through open source and open discussion, we can come to the compromise that will make a product that is useful for many, many people.
-- Brian Moon Senior Web Engineer ------------------------------ When you care enough to spend the very least. http://dealnews.com/ _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
