Re: Suggestion for EDS
- Posted by Robert Craig <rds at RapidEuphoria.com> May 24, 2001
- 415 views
Aku writes: > 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. EDS only uses one byte per character for strings (except for extremely rare cases where 2 bytes might be used). There's also a couple of bytes of overhead. See compress()/decompress() in database.e > 2. can make autonumber especially for record keys. > and add indexing in same file (.edb) for record data. I'll think about it. > 3. add encryption with password The data is already slightly encrypted, i.e. you can't load a .edb file into an editor and visually read the strings or the numbers. I'm not sure I want to implement one of the strong encryption algorithms. There are still some U.S. export restrictions on encryption algorithms. I wouldn't want Euphoria to be banned from distribution by the large U.S. shareware sites. Regards, Rob Craig Rapid Deployment Software http://www.RapidEuphoria.com