Hello guys,
We merged services DB's and ran with em a while good.
But now, real bad issues come up.
Features i request are:
1. ORE graph of Database
2. RDBMS backend, fully usable ( drop off these db files plz! )
( think of using table lockings and transactions, guys!!! )
- Try stay within SQL standard and provide db modules for major database backends like, postgres, MySQL, ... , oracle, sybase, adabas, db2, whatever..
- People would more likely develop codes if they can easily and understandable look over your db structure.
3. database sanity tool -> reports and fixes DB
( MAJOR ISSUE )
anopes service db doesnt show up sanity to me.
A sane database structure would not allow collisions or broken dbs...
If your in need of someone to provide standard database access code snippets, i can write you database access modules for postgres and maybe other ones.
The other thing which has to come from your side is use of standard SQL language, which offers all you need to do this data access and lock stuff.
Im lookin forward for comments.