Dan Pascu <[EMAIL PROTECTED]> writes: > Following the discussion we had about 2 months ago about having sqlobject > raise a set of exceptions independent of the backend used, I asked a > colleague of mine to implement this.
This sounds like a very good idea to me! I'm currently using a sqlite database for ease of configuration and testing, but for real use people might want to use another existing database. So it would be cool to be able to switch at a whim without having to change occurances of, say, sqlite.IntegrityError to mysql.IntegrityError (or whatever the corresponding exception might be called...). I realize that I could alias IntegrityError to one or another myself, but it would still be cleaner if SQLObject did it for me. -- Martin Geisler --- <[EMAIL PROTECTED]> --- http://mgeisler.net Read, write, create Exif data in PHP with PEL: http://pel.sf.net Take control of your webserver with PHP Shell: http://phpshell.sf.net
pgpfpgBn8LKLF.pgp
Description: PGP signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
