dbwrapper/dbpgsql/dbpgsqlgather.. This is a database wrapper so we canintergrate gnome-db into the system without problems.  This is handled by a#define for database backend at compile time.  The dbpgsqlgather is specificto whatever database backend your using and how to get that data from thedatabase.dbobject is completely redone from scratch. A lot of functions were dumpedbut still a lot of other functions need writing.  This depends on a lot ofthe new functions. Big differences are it has a store of ids for fields itsread from and also the write cache is built into the object. (reverse of howit operated before).  A lot of new structures here and a lot of stuff stillto be written.  file is a lot smaller now.dbuniqueid, a new function. This is for id's. So no longer is everythingdone on postgresql oid field, but handled by this file so it'll work withother database backends.db, I've restructued the API.  This wil be the main api file. new functionslike db_sql replace db_specialsql. db_getvalue replaces db_getfieldstr.  Youno longer need to create an object before you use it, and table name isoptional. however you need to specify tablename in order to write a newobject back to database. (you do need to know what table your saving to).Also another thing is that db_getvalue get will tie in with a lot of otherfunctions directly like db_getdefaults etc.dbbucracatt... (not spelt correclty) this is a global structure of everydatabase object created. Nice to know for memory links. But also to allow usto know when object changes it effects another object so update its datadbtoliet.  This takes over a lot of the dbobject functions.  This will dothe write backs and record where changes occur. though the changes are nowstored directly in a database object and not in a sperate write cache.  dblog. This is a log of every object that changes. Useful for user interfaceso it knows when to refresh widgets.dboopath is renamed to dbpathdbobjectvalid needs all its rules completely re-thought though cause of thechange in processes.dbobjectbirth will mark how an object came into existance so it can be usedfor checking for data effecting data.  I'm hoping all this is going to be thread safe but i dont know till i trycause tahts the next thing thats happening.  A number of the new files willbe running in completely different threads. Like writing to database will bein different thread to reading, checking for log changes will be in anotherthread as well..  hmm lots of threading..