compatibility between database platforms
It would be very easy to switch from one database server to another, All
your application is to do is to handle the database connection routines
while everything else are done by the stored procedures you have written in
your database.
Having two stored procedures for example "AddNewClient" both in SQL Server
and Firebird can do the same thing in two different ways yielding to the
same result. At your application side you will always call this procedure
without modifying anything, whereas if you were using data aware components
to connect to SQL Server databases for example you had to remodify your
whole application to migrate to Firebird.
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Behalf
Of Jangita
Sent: Friday, April 28, 2006 10:11 AM
To: [email protected]
Subject: Re: [delphi-en] Re: Why not use use db-aware controls.
my secret of coding: keep it as basic as you can, where you can. and
depend on as little as you can.... (dont tell everyone!)
kevin wrote:
> ----- Original Message -----
> From: "Glenn Lawler" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Thursday, April 27, 2006 3:36 PM
> Subject: [delphi-en] Re: Why not use use db-aware controls.
>
>
>>> What are compelling reasons not to use db-aware controls?
>> When you are writing Client-Server systems, using standard controls
>> instead of db-aware controls gives you a great deal of flexibility.
>> For example, all the db-aware controls I have used will lose their
>> data
>> as soon as you disconnect from the database. When using standard
>> controls. You can connect to the database, run a query to return data,
>> populate your controls, and disconnect. This frees up a database
>> connection. Most commercial Client-Server databases have a non-trivial
>> cost for each simultaneous database connection.
>>
>> There are many other reasons, this is just one. If you want your
>> applications to work exactly the way you want, using someone
>> else's component could cause you as much work as writing you own
>> code when trying to get around undesired component behavior.
>>
>> Glenn Lawler
>
> I would heartily agree with all these arguments, especially the last one;
>
> Ever been given a Delphi 3 project to update or modify, which has heavy
use
> of visual components (data-aware), the components naturally not being
> included with the original code, the project being uncompilable without
> them, having first to identify where they came from, or to find that they
> are not available for D2005, having to substitute them with other
> components, find solutions for their altered functionality, rewrite chunks
> of code, recheck everything;
> All that when the client only wanted a few modifications or a cloned form:
> I would hate to imply that my fondness for data-aware components is not of
> unmeasurable dimension;
>
>
>
>
> -----------------------------------------------------
> Home page: http://groups.yahoo.com/group/delphi-en/
> To unsubscribe: [EMAIL PROTECTED]
> Yahoo! Groups Links
>
>
>
>
>
>
>
-----------------------------------------------------
Home page: http://groups.yahoo.com/group/delphi-en/
To unsubscribe: [EMAIL PROTECTED]
Yahoo! Groups Links
-----------------------------------------------------
Home page: http://groups.yahoo.com/group/delphi-en/
To unsubscribe: [EMAIL PROTECTED]
SPONSORED LINKS
| C programming language | Computer programming languages | Java programming language |
| The c programming language | C programming language | Concept of programming language |
YAHOO! GROUPS LINKS
- Visit your group "delphi-en" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
