Re: TADOStoredProc
- From: "Dmitry Arefiev [da-soft.com]" <darefiev@xxxxxxxxxxx>
- Date: Thu, 11 Oct 2007 10:07:35 +0400
For instance. TAdoQuery sets the SQL using a Tstringlist while
TadoDataset uses a Widestring;
That is not good example, really. From D2006 the SQL is of type TWideStrings class. Similar about performance. One can write:
with SQL do begin
BeginUpdate;
SQL.Add('SELECT....');
SQL.Add('FROM ....');
SQL.Add('ORDER BY....');
EndUpdate;
end;
or can write
CommandText := 'SELECT ...';
CommandText := CommandText + 'FROM ....';
I prefer first way <g>
I know few extremely large application built on TADOQuery,
TADOStoredProc. And there is nothing, what these application
can get additionally, if they will use TADOCommand & TADODataSet.
TADOCommand & TADODataSet usage will give you more explicit / natural control on recorset manipulations, briefcase model, persistence,
etc. Just if application is needing that ...
Regards,
Dmitry
--
Dmitry Arefiev - www.da-soft.com
AnyDAC - Oracle, MySQL, MSSQL, MSAccess, IBM DB2, Sybase
ASA, Interbase/Firebird, DbExpress, ODBC data access engine
ThinDAC - multitier data access engine
.
- References:
- TADOStoredProc
- From: Alan T
- Re: TADOStoredProc
- From: Brian Bushay TeamB
- Re: TADOStoredProc
- From: Niklas Larsson
- Re: TADOStoredProc
- From: Brian Bushay TeamB
- Re: TADOStoredProc
- From: Nigel Jones
- Re: TADOStoredProc
- From: Brian Bushay TeamB
- TADOStoredProc
- Prev by Date: Re: TADOStoredProc
- Next by Date: Determining parameter in TADOStoredProc
- Previous by thread: Re: TADOStoredProc
- Next by thread: Re: TADOStoredProc
- Index(es):
Relevant Pages
|