On Mon, Jun 21, 2010 at 04:14:10PM +0100, David Goodenough wrote: > On Monday 21 June 2010, Lew wrote: > > Sim Zacks wrote: > > >> database agnostic code is theoretically a great idea. However, you > lose > > >> most of the advantages of the chosen database engine. For > example, if > > >> you support an engine that does not support relational integrity you > > >> cannot use delete cascades. > > >> The most efficient way is to have a separate backend module per > > > > > > database > > > > > >> (or db version) supported. The quickest way is to write code that will > > >> work on any db but won't take advantage of db-specific features. > > > > David Goodenough wrote: > > > This is what I am trying to encourage. I am asking about the best > > > way to encourage it. > > > > You want to encourage the use of databases that don't support relational > > integrity? > no, I want to encourage "The quickest way is to write code that will > work on any db but won't take advantage of db-specific features." As with phrases like, "the quickest way to grill a unicorn steak," that it can be stated in a few words does not make in possible. Cheers, David. -- David Fetter <david@xxxxxxxxxx> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@xxxxxxxxx iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
