1. EDS 2 questions
Hi everybody
1- Lets suppose I have a database with 100 records but each record has
very big data sequences say 100,000 elements. Would EDS try to load
entire records for an append or an insert or maitain its disk blocks
allocation as per database.e and load only a portion of the data?
2- How many concurrent open tables does EDS support?
TIA for your help
Regards
Serge Lavigne
2. Re: EDS 2 questions
jondolar wrote:
> 1- Lets suppose I have a database with 100 records but each record has
> very big data sequences say 100,000 elements. Would EDS try to load
> entire records for an append or an insert or maitain its disk blocks
> allocation as per database.e and load only a portion of the data?
Using the functions in database.e, you have to read or write
an entire record (actually, the data or the key).
There is no way to directly update just a small portion of
one record on disk.
If you read the data for a record, append to it,
and write it back, EDS will try to store it in the same place
on disk if there's enough space, but otherwise EDS
will look for a big enough empty space in the .edb file.
As a last resort, EDS will store the data at the end of
the .edb file, thereby making the file bigger.
> 2- How many concurrent open tables does EDS support?
There is always one "current" database and one "current"
table. There are functions for choosing a new current
database and new current table. A database could have
millions of tables. If you want to copy data from one
table to another, you have to call a routine to explicitly
switch back and forth between the two tables.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: EDS 2 questions
jondolar wrote:
> Thanks Rob for the straight answer. Do you intend, eventually, to buffer
> reading/writing to disk in some future versions making EDS a true
> diskbase DBMS?
I'm not sure what you mean by "true diskbase DBMS".
My intention in developing EDS was not to compete
with high-performance transaction processing systems.
I just wanted a really simple, flexible way for
Euphoria programmers to store and retrieve Euphoria data.
I've personally found EDS to be useful in more
situations than I originally expected.
It's nice to be able to store any kind of complex
variable-size sequence in a record. Other database
systems force you to have a fixed number of fields,
with each field limited to a fixed-size data type.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
