Re: A thought about other open source projects

then you want your code to call stub functions (with DBSpecific stack parameters)
Insert
Update
Delete(-with-cascade)
Select
 
I ran into a problem recently where i wanted to LOCK table MySQL which of course is a no-op in MySQL so I carried the driver string as a stack param e.g.
public int Lock(String driver_string_stack_param)
if(driver_string_stack_param.equalsIgnoreCase("com.mysql.jdbc.Driver") ; //noop
else{
//      do Lock Logic
     }

hth
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

 
> From: david.goodenough@btconnect.com
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] A thought about other open source projects
> Date: Mon, 21 Jun 2010 16:14:10 +0100
>
> 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."
>
> David
> >
> > Really?
> >
> > I think that is a simply terrible idea.
> >
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

---

The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy.