On Saturday 08 April 2006 01:08, [EMAIL PROTECTED] wrote: > If you made a field too short for some of the data which comes along > there are two different approaches as to how to handle the situation. > First is to identify the problem and roll back so that nothing even got > started. This is what "real" RDMSs apparently do.
Say what? A real RDBMS does not roll back transacations when you failed to design your fields properly or when you modify a table. > Second is to keep going and minimize the damage as best you can. I dont really understand what youre trying to say. Keep going and minimize damage? How would you do that when your fields are too small? And what has this got to do with PostgreSQl v.s mySql anyway? > This is what systems that face the "real world" are forced to do. Are you saying that "real" RDBMS' arent used in the real world? > There was a crack in this about MySQL being an SQL-looking front end > to a file system. Actually very perceptive. You can use the filesytem > to move stuff around and get away with it very nicesly. Perhaps that is becuase mySql seems to be very often used as a glorified replacement for flatfiles, especially by webdesigners. > As to losing data, I suspect you'd lose a lot more > from PostgreSQL than MySQL on a failing hard drive. I seriously doubt that. ---- Larts Hansson
