On Sunday 18 November 2007 02:40:19 am Uwe Grauer wrote: > Dennis Lee Bieber wrote: > > On Sat, 17 Nov 2007 07:53:07 -0800, johnf > > <[EMAIL PROTECTED]> declaimed the following in > > > > gmane.comp.python.dabo.user: > >> Postgres, Firebird, MsSQL do. I would guess MySQL too. Know nothing > >> about SQLite. > > > > MySQL, based upon my books, only supports referential integrity > > options for InnoDB tables. It takes the syntax for any table type, but > > actual checks and cascades only work for the one. > > > > SQLite doesn't seem to do cascades -- though it may be possible to > > fake it via triggers... > > I knew that there were some special reasons why i decided to do it in > such a way that i use the database just for simple integrity rules and > let the app logic do the work which can't be implemented in a portable > way across various database backends. > If i don't want to support different database backends, i for sure would > use constraints, triggers and stored procs to do all the work. > > Uwe
Does not look like SQLite supports what you are currently doing - preventing deletes. Of course again you can fake it by using Triggers. Using universal database frameworks like SQLAlchemy 0.4 and Dabo can't really take advanage of the power/features of each of the databases they support. In my case I use what Dabo has available and what Postgres has available. That way I have the best of both worlds. In your case I would recommend that you limit the portability to a few that support cascade deletes. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
