Hi Jeff;
There is some talk about using PL/Perl. However, since there is also
some concern about unnecessary dependencies if people want to have
implementations in other languages (like Python), I am starting with
PL/Pgsql for my contributions since that seems the safest option :-)
Also, I person
--- Chris Travers <[EMAIL PROTECTED]> wrote:
> Since 1.3 will be our first release with substantial logic
> encapsulated in the database, I wanted to get discussion started on
> coding conventions. Currently we are targetting the code for
> PostgreSQL 8.0 through 8.2 but want to ensure it is reaso
Hi all;
Since 1.3 will be our first release with substantial logic
encapsulated in the database, I wanted to get discussion started on
coding conventions. Currently we are targetting the code for
PostgreSQL 8.0 through 8.2 but want to ensure it is reasonably
future-safe. My own thinking is that
Ok. Try creating the ledger-smb.conf file first. This would be done
by copying the ledger-smb.conf.default to that name. Then edit it to
point to your central database. The documentation is a little
misleading because you need to do the rest of installation before the
build test will complete s
I downloaded ledger-smb-1.2.0rc1.tar.gz, unpacked it, installed the
dependencies from the Debian archive (Unstable), ran 'perl Build.PL' with no
errors, and then ran './Build test' with the following results:
t/01-load...Useless use of a variable in void context at
/home/john/ledgersm
