1. Re: RDMS Database's and/or Record Managers What good is Euphoria?
- Posted by "Kat" <gertie at visionsix.com> Jan 23, 2004
- 435 views
On 22 Jan 2004, at 23:43, Isaac Raway wrote: > > > Kat wrote: > > >On 22 Jan 2004, at 10:53, Isaac Raway wrote: > > > >>Play toy? Dude. This is a euphoria mailing list. Might not want to call > >>the language a "play toy" in such company. > >> > >>Business applications are lightweight on the actual code. What's > >>important is the database. That might be a bit trickier because there > >>aren't many available for Euphoria, but it is no reflection on the language. > >> > >> > >What do you want that is not already in strtok? > > > > > Well, I've never used strtok, but I will give it a try now that you > mention it. It looks to be most useful for parsing source code (which is > great), but not for creating a database. Databases should not be doing > any string tokenization of any kind. That wouldn't be a database, it'd > be a flat text file. Strtok was written to do data handling as far away from strict Pascal and C records as possible. Been there, done that, not again. > Databases use virtual file systems with paged > storage methods and separate indexes, and most importantly, always > access their data files in a binary fashion. Not always. I found most of my accesses are wildmatches. Can't do a btree with wildcards. And as for "relational", Tiggr's has pointers to other data items, executeable code, etc. And the db is not stored in memory. And the contents are not fixed in any way or form. If i turn her lose, there is no way the 5 gigs of data can be put in a Eu sequence in memory,, i'd need 20gig to load it, and another 40gig to manipulate it, and i don't have the money to waste like that. How you store and access the data on the drive is not strtok's business. But recently, someone asked about the access speed for a 1meg file, i gave code to read it in one sec, and parse the lines out in 1-2 sec (233mhz cpu), as if each line was a data item. Each line could have held separate fields, free form lengths, and each of those could have held more fields, etc etc. YMMV Kat