RE: Suggestion for EDS

new topic     » topic index » view thread      » older message » newer message

> -----Original Message-----
> From: aku at inbox.as [mailto:aku at inbox.as]

> Suggestion for EDS:
 
> 1. if user stores a sequence, make EDS can check if it is
>    a string (all bytes 0-255). If yes, store as string (just use 1
>    byte per atom). If not, store as usual. If this is make EDS slower
>    make function enable_string() and disable_string() for example.
>    So I can store contents of a 1 MB file without having a 4 MB .edb
>    file.

That's a pretty good idea.  However, I think RDS is pretty busy right now,
and EDS is at the bottom of the list.  Why don't you take a crack at it?
Take a look at compress() and decompress() in database.e.  That's where it
all happens.
 
> 2. can make autonumber especially for record keys. and add indexing
>    in same file (.edb) for record data.

This one is a lot tougher (well, a simple autonumber scheme should be easy
for keys).  I'm working on indexing record data for EuSQL.  I'm able to
store and retrieve the indices, but using them intelligently is a bit more
involved.

> 3. add encryption with password.

This sounds like a good idea, as well.  There are several encryption libs in
the archive.  It should just be a matter of wrapping all I/O for EDS.  Go
for it.  

Matt Lewis

PS, if you added [some of] these things to database.e and submitted to the
user contributions, I'd probably vote for it...

new topic     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu