<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff background="">
<DIV><FONT face=Arial size=2>Hi Ruslan,<BR><BR>----- Original Message -----
<BR>From: "Ruslan Zasukhin" <sunshine@public.kherson.ua><BR>To:
<valentina-beta@lists.macserve.net><BR>Sent: Tuesday, June 21, 2005 2:34
PM<BR>Subject: Re: V4MD request<BR><BR><BR>> On 6/21/05 3:19 PM,
"info@vallemediatime.com" <info@vallemediatime.com><BR>> wrote:<BR>>
<BR>> > Right,<BR>> > now, after this new explanation I have better
understand some others<BR>> > differences about API-SQL<BR>> > I'm
still tried my project with more API calls; at beginning (V2.0.1) it<BR>>
> seems to me that API was more slowly... now is better but not how SQL
query.<BR>> <BR>> Hmm. You say that for you API way works slower of SQL
???<BR>> This is not true. <BR>I say that: "for get data from db and show it
in a grid is more slowly... or more probably I use a non optimizing
script...<BR>N.B. sprite(n) contains cXtraStringGrid</FONT></DIV>
<DIV><BR><FONT face=Arial size=2>on ProduceTableData (n, rs, table)<BR>myData =
[]<BR>fieldCount = table.fieldCount<BR>-- GRID COL HEADERS</FONT></DIV>
<DIV><FONT face=Arial size=2>sprite(n).colCount =
gHeaderList.count<BR>sprite(n).SetRow(0, string(gHeaderList))<BR>-- TABLE
ROWS<BR>recCount = rs.itemCount<BR>if recCount > 0 then<BR>iter =
rs.makeNewIterator()<BR>if iter.firstItem() then<BR>repeat with i = 1 to
recCount<BR>row = []<BR>table.RecId = iter.value<BR>repeat with j = 0 to
gHeaderList.count<BR>f = table.field(j)<BR>row[symbol(f.name)] =
f.value<BR>sprite(n).SetCellText(j, i, string(f.value))<BR>end
repeat<BR>myData[i + 1] = row<BR>iter.nextItem()<BR>-- GRID
ROWS<BR>sprite(n).rowCount = myData.count<BR>end repeat<BR>end if<BR>end if
<BR>sprite(n).ColAutoSize()<BR>end<BR><BR>> Aha, may be you repeat mistake
and try to work with API way thinking about<BR>> features of SQL way as joing
?<BR>> <BR>> Remember 2 months ago on beta list was discussion about
this.<BR>yes, you have good memory :-)</FONT></DIV>
<DIV><FONT face=Arial size=2> <BR>> If to use API way correctly it can
be MANY TIMES faster of SQL way.<BR> <BR>> <BR>> > At last,
for my project I hope that API is better way, (I have seen some<BR>> > SQL
problems about the case_insensitive and apostrophe... that you know)<BR>>
<BR>> I think there is no real problems. Just you need do steps as
using<BR>> Valentina.EscapeString()<BR>I think
that if the string change every time is necessary to detect every time
where insert Escape...</FONT></DIV>
<DIV><BR><FONT face=Arial size=2>> <BR>> > If you have time in the next
days, months? I ask you:<BR>> > "It would appeal to me to have a doc-table
that clears just in which<BR>> > circumstances is preferibile to use API
or SQL"<BR>> <BR>> I have told this several times.<BR>I know,</FONT></DIV>
<DIV><FONT face=Arial size=2>but every a lot is necessary a good ones
reassumed :-)</FONT></DIV>
<DIV><FONT face=Arial size=2><BR>> Please search beta list for
April-May.</FONT></DIV>
<DIV><FONT face=Arial size=2>done</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Thank Paolo</FONT></DIV>
<DIV><FONT face=Arial size=2> </DIV>
<DIV><BR>> <BR>> -- <BR>> Best regards,<BR>> <BR>> Ruslan
Zasukhin<BR>> VP Engineering and New Technology<BR>> Paradigma Software,
Inc<BR>> <BR>> Valentina - Joining Worlds of Information<BR>>
http://www.paradigmasoft.com<BR>> <BR>> [I feel the need: the need for
speed]<BR>> <BR>> <BR>>
_______________________________________________<BR>> Valentina-beta mailing
list<BR>> Valentina-beta@lists.macserve.net<BR>>
http://lists.macserve.net/mailman/listinfo/valentina-beta<BR>> <BR>>
<BR>> <BR>> -- <BR>> No virus found in this incoming message.<BR>>
Checked by AVG Anti-Virus.<BR>> Version: 7.0.323 / Virus Database: 267.7.8/22
- Release Date: 17/06/2005<BR>> <BR>> </FONT></DIV></BODY></HTML>