Re: [Openledger-developer] Impl. of "general ledger transaction"

[Klavs K. <kl...@vs...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

on 02-03-2005 19:52 Michael Long wrote:
[SNIP]

| I believe I was the one that mentioned that. To configure you
| server to log all SQL statements to the log file modify
| postgres.conf. Look for the line: #log_statement = 'none' and
| change it to: log_statement = 'all'

Thanks - I'll do that.
[SNIP]

| After several months of distractions I have begun looking at the
| CGI-Formbuilder and Template-Toolkit perl modules as possible
| solutions to separating the API layer from presentation layer. Has
| anyone had experience with these?

I've used Template Toolkit for letters and other things needing
templating, it works quite well. Haven't used CGI-Formbuilder.

It's fine reimplementing the GUI - except if you want to start doing
that BEFORE we the API is half-done - we need to agree on a list of
functions(and parameters) the API should have, so you can code against
that.

Something like:
postTransaction($transactionobject,$employeeid)
postInvoice($invoiceobject,$employeeid)

etc. ?

- --
Regards,
Klavs Klavsen, GSEC - kl...@vs... - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8  B8DA 3D3A 0B79 7E06 3C62

"Those who do not understand Unix are condemned to reinvent it, poorly."
~  --Henry Spencer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCJrWuPToLeX4GPGIRAjCQAJ4/m4nV0VpU+jKkTb724+TzMSS2xQCgoapu
6O+asEF9tWi23M2LTkhubMU=
=OkLI
-----END PGP SIGNATURE-----