Posted by: Anonymous Coward
on November 12, 2006 05:29 AM
LedgerSMB 2.0 will probably have little to no SQL-Ledger code in it.
That's good to hear! Good luck with your project; I'm following it keenly.
Tighter integration with Sugar is largely limited by MySQL in your case (you can pull data from MySQL into PostgreSQL without too much problem, and you can push from PostgreSQL into MySQL, but when you need real-time updates from MySQL, you have a problem).
A push model is fine for me; we already have scads of Perl scaffolding connecting Sugar <-> Asterisk <-> SQL-Ledger <-> Our download authorization database. For example, one of the neat things we have: When a customer calls tech support, we automatically get a new tab in Firefox showing the Sugar data, a list of invoices and whether or not they've been paid, and a list of open RT tickets.
We just need a standard, modular way to add hooks into SQL-Ledger to kick off our push scripts.
Learn about Linux
Download Linux
Get Linux help
Re:We use it
Posted by: Anonymous Coward on November 12, 2006 05:29 AMLedgerSMB 2.0 will probably have little to no SQL-Ledger code in it.
That's good to hear! Good luck with your project; I'm following it keenly.
Tighter integration with Sugar is largely limited by MySQL in your case (you can pull data from MySQL into PostgreSQL without too much problem, and you can push from PostgreSQL into MySQL, but when you need real-time updates from MySQL, you have a problem).
A push model is fine for me; we already have scads of Perl scaffolding connecting Sugar <-> Asterisk <-> SQL-Ledger <-> Our download authorization database. For example, one of the neat things we have: When a customer calls tech support, we automatically get a new tab in Firefox showing the Sugar data, a list of invoices and whether or not they've been paid, and a list of open RT tickets.
We just need a standard, modular way to add hooks into SQL-Ledger to kick off our push scripts.
#