V4MD (class VTable) go to a specific record and some API
question
info at vallemediatime.com
info at vallemediatime.com
Mon Mar 28 22:22:24 CST 2005
Thanks for your exhausting explanations :-)
Now I'm working in off-line database and so I will try the new API way.
Paolo
----- Original Message -----
From: "Ruslan Zasukhin" <sunshine at public.kherson.ua>
To: <valentina-beta at lists.macserve.net>; <valentina at lists.macserve.net>
Sent: Monday, March 28, 2005 9:50 PM
Subject: Re: V4MD (class VTable) go to a specific record and some API
question
> On 3/28/05 9:30 PM, "info at vallemediatime.com" <info at vallemediatime.com>
> wrote:
>
> > Hi Ruslan,
>
> > I am tryng the API methods instead of SQL cursor and I've some question:
>
> > 1. how can I go to n record (I look at pag.56-57 of Director
Reference...
> > Table.firstRecord() etc. but I don't understand how to go to a specific
> > record...)
>
> Table.RecID = pos
>
>
> > 2. in general can you tell me and list the major differences between
VCursor
> > and API method?
>
> API methods do not use SQL at all.
> Big difference? :-)
>
> > Now is better continue to use VCursor (like v.1.1) or pass to API
method?
>
> All depend on task, your skill, your favor,
>
> I think RULE should be next:
>
> * exists many books and experts that know SQL and cursors.
> so if you have urgent project and other problematic issues
> then use SQL.
>
> * IF you want to study new API way,
> if you feel that SQL is not fast enough for you
> if you just like what you read about API way
>
> Then try this new style of db coding.
>
>
> > Where are some limits of API respect VCursor?
>
> API way is bad for REMOTE SERVERS.
> So if you plan to have client server then avoid API.
>
> In the same time we have implement API methods for server protocol also.
> We think that in local intranet it also can work fine.
> You know that new fast ethernet works sometimes even faster of HDDs.
>
> > And the performance... what is more fast?
>
> API Way of course.
>
> in the same time if you will think in SQL way
> and try do API coding in SQL way, then you will get problems.
>
> btw, Oliver have step over this barrier :-)
> Oliver may be you can add your story?
>
> for example, it is bad idea to do join using API methods.
> will be slower of SQL.
>
> API methods are intended for NAVIGATIONAL Database model.
> read about it in Valentina Kernel.pdf
>
> Navigational model require other thinking, other GUI, ...
>
> --
> Best regards,
>
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc
>
> Valentina - Joining Worlds of Information
> http://www.paradigmasoft.com
>
> [I feel the need: the need for speed]
>
>
> _______________________________________________
> Valentina-beta mailing list
> Valentina-beta at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina-beta
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27/03/2005
>
>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.8.4 - Release Date: 27/03/2005
More information about the Valentina-beta
mailing list