> >From the developer perspective, the current XML storage is a pain to > deal with. The SQL backend would have multiple advantages... > > 1/ direct query support > 2/ real transactional changes > 3/ No seperate "save" operation [with the associated data-loss window] > -- lower crash-effect potential. > 4/ Easier path to multi-user access. > > Granted, only '3' would be directly visible to users, but happier developers > generally = more/better features. :)
Reason #5... 5/ Adding extra tables is pretty trivial, and does not require coding extra DTDs or schema. -- select 'cbbrowne' || '@' || 'ntlug.org'; http://www3.sympatico.ca/cbbrowne/spreadsheets.html Rules of the Evil Overlord #9. "I will not include a self-destruct mechanism unless absolutely necessary. If it is necessary, it will not be a large red button labelled "Danger: Do Not Push". The big red button marked "Do Not Push" will instead trigger a spray of bullets on anyone stupid enough to disregard it. Similarly, the ON/OFF switch will not clearly be labelled as such." <http://www.eviloverlord.com/> _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
