Re: data base access
George Walters writes:
> the 'current table' issue would still be a problem in
> a program reading from so many different data bases.
EDS was designed with the idea of having
a "current table" and a "current database".
This was done mainly to reduce the number of arguments
to be passed on the various database operations.
If you are randomly accessing many different tables,
this approach won't be as nice as one where you specify
the database and table on every call.
I doubt that performance will be an issue,
since db_select() takes only
a few microseconds to choose a new database, and no file
is opened or closed. db_select_table() reads
in 4 bytes per record from the table, but this data is likely
cached in memory, so no disk access would be required.
Again, we are talking microseconds.
If you are getting input data from a user, then you will
spend a lot longer waiting for the user to type one keystroke
than you will spend doing a typical database update.
If Jonas has alternate routines that let you
avoid explicitly selecting a database and table,
then you should probably use them. I don't plan to
add routines like that to EDS. I'd rather that
other people add extra layers of code to
suit their needs and their taste.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
|
Not Categorized, Please Help
|
|
