Re: Database Independance

From: Dennis Landi ([none][at][none][dot][com])
Date: 03/05/04 

Date: Thu, 4 Mar 2004 19:28:28 -0500

"Xavier Pacheco (Xapware)" <xavier@spamlessxapware.com> wrote in message
news:4047ac55$1@newsgroups.borland.com...
>
> I'd like to get a collection of practices that one should take when
> writing a Delphi application and where you desire database independance
> with SQL database. What are some things to avoid? Some things to do?
>
> for instance
>
> 1. Don't use long table names (Interbase/Firebird has a limit on the
> tablename length).
>
> 2. Stick with a specific case on metadata
>
> that sort of stuff. Comments?

Put a broker between you SQL Server implementation and your application
logic.

App << >> Broker << >> SQL_Server_?

Now you Application Logic is insulated from your backend implementation
altogether...

Make you broker interface-based so that you can swap in a Broker_Version for
specific back-end when necessary while still serving up to the app your
IBroker interface when requested....

Put your interfaced broker in an interfaced run-time package (plug-in) for
extra credit.... <g> Then its ready for deployment in, say, a
shrink-wrapped enterprise product that needs to target any number of
commercial backends...

-d

Relevant Pages

  • Re: Serializing an interface
    ... What exactly to the declared variables in your orchestration look like? ... you have one reference to the broker, and one or more to this interface?) ... I have a .net interface which only use simple types. ...
    (microsoft.public.biztalk.general)
  • ANN: toamqp 0.3.1
    ... toamqp will allow you to transport thriftmessages via an AMQP ... broker. ... The interface makes this really super-easy - allowing you to ...
    (comp.lang.ruby)