Considering a fork for implementing MySQL C library (multi-user) - thoughts?

[stuartb]

Hi John

Thanks for the comprehensive reply.  Sorry for the confusion, I am aware of
GNU - bad choice of abbreviation. 

Regarding GPL, no problem, we currently work with other open source projects
for the same reasons (Alfresco being a good example).  Rather than re-create
every module from scratch we prefer to adopt a middleware approach and
bridge existing systems together.   We can then query those systems via
API's or the database directly to present this data to the user in various
ways.  Our own product follows an SOA approach which allows us to bolt on
different services depending on our clients needs.   This is what brings us
to gnucash.

Just to confirm; the method you proposed was our first idea, maintaining our
existing database structure but constructing a synchronization module to
keep the two datasets in sync.   This would keep the projects completely
separate and allow us to maintain the use of triggers and database
transactions.

On reflection, the loading of the dataset may not be such an issue if
gnucash was viewed as a read only reporting module (multiple users could
also synchronize the master dataset).  Our larger clients already run
existing server-side accounting systems which we feed data to using web
services - the gnucash connector would allow us to provide an alternative to
the smaller MGAs which we deal with, who already use Quickbooks and Sage and
are looking for alternatives.

Can I confirm; if a record is modified in the database - are you updating
the entire mysql dataset, or just pushing the changes ?



--
View this message in context: http://gnucash.1415818.n4.nabble.com/Considering-a-fork-for-implementing-MySQL-C-library-multi-user-thoughts-tp4674947p4674974.html
Sent from the GnuCash - Dev mailing list archive at Nabble.com.