Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Shoud I ???
Message
 
À
02/05/2001 21:51:31
Walter Meester
HoogkarspelPays-Bas
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Titre:
Divers
Thread ID:
00502777
Message ID:
00502847
Vues:
17
Just to put in my two cents. (since you are asking)
1 I find myself using sql selects all the time - and glad I do. learing the sql language is - in my opinion, is a benefit that you will enjoy for years to come. the sql syntax is not going away.

Add to that, using select - to create joins, for reports, and picking lists, is MUCH faster than using set relation to - set skip to and those old xbase type commands. Personally I find working with cursors since they are on the local machine much faster in general, that working with only a network file share..

I agree with Mike, on the use of replace.

in the long run, if you have to at sometime merge your data to sql server - getting to understand the sql syntax now. has no speed drawbacks, (that I can tell) and only the benefit of more powerfull querries... and so on.

Once I started using sql type commands about a year ago. I cant think of very much code which I use with seek anymore.

Thats just my two cents.

Bob Lee


>Hi plinio,
>
>The xBase commands (SEEK, REPLACE, DELETE) etc are different than the SQL commands:
>
>1. Since the xBase commands are record oriented, they are faster when handling the current record (DELETE, REPLACE). SEEK is always faster than SQL-SELECT to search for records.
>
>2. xBase commands operate on buffered tables while SQL commands ignore buffered changes until they are commited.
>
>3. SQL commands are set oriented, meaning that they are good at handling more than one record. The SQL - SELECT in particular is powerfull to do fast calculations with data. Personally I don't use SQL - DELETE or SQL - UPDATE a lot. They're a bit more limited compared with REPLACE and DELETE (Buffering changes, replacing in more than one table at once, Record vs Table locks etc.)
>
>Personally, I think that with the xBase commands give you just a bit more control and performance in particular cases. SQL SELECT on the other hand gives you a very powerfull mechanism to query your tables fast and efficient (thus without doing a lot of xBase calculations).
>
>I find that it depends on the given situation, for one xBase is far better, for others SQL is the clear winner.
>
>Walter,
>
>
>
>>Shoud I replace the use of : SEEK,REPLACE,DELETE and use SELECT * FROm where, Update WHERE, and DELETE FOR
>>
>>It's a good artinative??
>>What's the diferences?? (speed,integrity???)
In the beginning, there was a command prompt, and all was well.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform