i hate mysql for truncating strings ... silently or for y == ü (very old mysql, but i will never forgot to not able to insert 'y' and 'ü' in a unique index column and the many hours to find the reason)
or crashing tables so often. i startet a delete on a 20 mio row table yesterday and hit CTRL-C to abort ... the table was crashed postgres seems sometimes slow direct compared with mysql selects, but i never had problems with postgres at that level. Am 15.04.2011 10:42, schrieb Eden Cardim: >>>>>> "Matija" == Matija Grabnar <[email protected]> writes: > Matija> Well, why did you turn off checking? It's a TOOL, a powerful > Matija> tool. Like all powerful tools, if you disabled the safeties, > Matija> you have to know what you're doing. Just like a power saw, > Matija> you can do very good work, or you can cut off your thumb. > > Matija> Screaming the tool is unsafe because you can disable the > Matija> safeties which are on by default is akin to crying for your > Matija> nanny to cool your milk so you don't get burned by the hot > Matija> hot hot cup. > > Disabling foreign keys is very useful for populating a database without > having to pre-calculate the insertion order in a database system that > doesn't support deferred constraints. So no, it's not a tool, it's a > lazy workaround, so ok, it's "useful", except that you do want the > database to check if you screwed anything up when you turn the > constraints back on, not doing that is just plain wrong and lazy (and > not the good type of lazyness). So, when it comes to bulk-loading data, > mysql simply leaves you no sane alternative. > > Also, the benchmarks I've seen of mysql vs. postgresql are always > comparing a select against a single myisam table, which is hardly fair > because it barely applies any constraints, so of course it'll be faster > than anything, just like writing to /dev/null. > > One more thing to add to the cases where mysql warns you of absolutely > nothing is when an integer overflow occurs, I've lost one too many hours > of my life and sanity debugging those cases. > -- Mit freundlichen Grüßen Felix Antonius Wilhelm Ostmann ----------------------------------------------------------- Websuche Search Technology GmbH & Co. KG Martinistraße 3, D-49080 Osnabrück ----------------------------------------------------------- Tel.: +49 (0) 541 40666 0, Fax: +49 (0) 541 40666 22 Email: [email protected], Web: www.websuche.de ----------------------------------------------------------- HRA 200252, AG Osnabrück, Ust-IdNr.: DE814737310 ----------------------------------------------------------- Komplementärin: Websuche Search Technology Verwaltungs GmbH HRB 200359, AG Osnabrück, Geschäftsführer: Ansas Meyer ----------------------------------------------------------- Die in dieser Email enthaltenen Informationen sind vertrau- lich zu behandeln und ausschließlich für den Adressaten be- stimmt. Jegliche Veröffentlichung, Verteilung oder sonstige in diesem Zusammenhang stehende Handlung wird ausdrücklich untersagt. _______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[email protected]
