On Fri, Sep 11, 2009 at 7:54 AM, Jules Stevenson <[email protected]> wrote: > > >> The main differences I've seen with MySQL compared to SQLite off the >> top of my head are: >> - Rigid column lengths (SQLite stores long values; MySQL truncates >> them with a warning) >> - Different date handling functions (you'll need if-blocks in your >> code; e.g., if engine.name=="mysql") >> - Different autoincrement policy (not really an issue) >> - String comparisons are case insensitive (though I think SQLite's >> LIKE is case-insensitive) > > Thanks Mike, much appreciated. I've found the rigid column lengths one,
That was one reason I gave up on MySQL for one site. The incoming data is not interactive but imported from several sources. I have no control over the lengths of these, so I didn't want the importer blowing up after I'm gone on any values that unexpectedly become longer than 255 or 65535 characters. MySQL has VARCHAR, TEXT, MEDIUMTEXT, and LONGTEXT, but only the first two correspond to SQLAlchemy's generic String and Text types. Which means I'd have to put MySQLisms in the code to choose LONGTEXT. Also, all these fields could be the target of an advanced search, in which case I'd have to do LIKE on them. That is not a big deal although I think searching on lots of text fields is less than ideal. You can't use indexes with them, although you can't use indexes for LIKE anyway. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
