Compact?

[Ruslan Zasukhin]

on 2/6/04 12:40 AM, Ken Ray at kray at sonsothunder.com wrote:

> 
>> In the same time, all BIG DBMS guys say:
>>     NEVER DEPEND on field order !!!
> 
> BigDBMS guys don't have SQLSelectRecords()... :-)
> 
> When I have several places in my code that retrieves data with
> SQLSelectRecords, I get back tab-delimited data, where I need to know
> specifically what's in each column. For example, if my Entites table has
> FirstName, MiddleName, and LastName fields, my code would say something
> like "put the first tab-delimited item into a variable for FirstName,
> put the second into a variable for MiddleName, and put the third into a
> variable for LastName". If adding a new field makes it FirstName,
> MiddleName, InsertedField, LastName, I have to change all the places in
> my code that says "the third tab-delimited item is LastName" (since it
> *isn't* anymore).

Ken, but what problems?

You always can do, and should do
    
    SELECT FirstName, MiddleName, InsertedField, LastName

But not 
    
    SELECT *

This is always good idea, because IF in future you ADD fields, your EXISTED
code will not be changed. Using SELECT * you start get MORE fields.



> Right now I'm adding dummy fields to fill the slots, then adding the
> "new" field, and then deleting the dummy fields.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------