thanks for the quick reply
yes, the whole reason for PQL.Manage is to make things easier for people, as well as a nice way to manage a database without burying yourself in code. PQL stores data in a format thats pretty much never going to be easily human readable. You have to first seek around the reference file that contains the location of the data, then after you get that, seek to where the data is in the data file... then you have to decrypt the data... its all really unappitizing stuff.
anyway, glad to hear you're interested, its hard to get people using something unfamiliar
pql is pretty robust, the pql manual runs on it... heck even a CMS, forum and blogging engine are in the works and being powered by it.
on my list of to-dos before 1.0 are
1. stop trying to debug the query JOIN functionality and add it to PQL (im still testing it... not too sure the different types behave as they should yet)
2. query caching, pretty important this one.
3. logical map caching, not too important but could save precious microseconds
4. implement the almost completed operator preceedence preparser (right now you can't use different logical operators in the same compound clause, this will give piority to &&, then ||, then ^^ by enclosing clauses in subclauses.)
5. conform to the ACID standards... this will be pretty tough for a flat-file DBMS but doable i hope.
and get more people using PQL!