Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- From: "Ian Boyd" <ian.borlandnews010@xxxxxxxxxxxx>
- Date: Thu, 16 Jun 2005 14:14:49 -0400
> What happens if you use:
> Query.Fields[i].Value
>
> It returns a variant.
Problem is that it doesn't actually return a variant.
If you look at the code:
function TStringField.GetAsVariant: Variant;
var
S: string;
begin
if GetValue(S) then Result := S else Result := Null;
end;
What it actually does it return a string, and then cast it to a variant.
Which is part of why ADOExpress is so slow.
.
- Follow-Ups:
- Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- From: Ian Boyd
- Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- References:
- ADO vs ADOExpress time trials. Not good for ADOExpress
- From: Ian Boyd
- Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- From: Ian Boyd
- Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- From: Bill Todd
- Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- From: Ian Boyd
- Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- From: Kostas Terzides
- ADO vs ADOExpress time trials. Not good for ADOExpress
- Prev by Date: Re: Aggregate fields and .IsNull
- Next by Date: Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- Previous by thread: Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- Next by thread: Re: ADO vs ADOExpress time trials. Not good for ADOExpress
- Index(es):
Relevant Pages
|
|