|
From: Ing. A. A. G. <ag...@ma...> - 2001-08-18 03:40:17
|
Federico:
Thanks for your comments. Some of those features you requesteed are
implemented in the new 1.6.0 version.
Help us to develop SQL-Ledger to live out of the endless upgrade cycle of
the Microsoft environment.
Regards,
Antonio Gallardo
-----Mensaje original-----
De: sql...@li...
[mailto:sql...@li...]En nombre de
Federico Sevilla III
Enviado el: Viernes, 17 de Agosto de 2001 09:04 p.m.
Para: SQL Ledger Mailing List
Asunto: SQL-Ledger Evaluation
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi everyone,
I'm the network administrator for our company, an SME based in the
Philippines. I'm working with our accounting department to hopefully get
SQL Ledger in place. We are currently using SQL-Ledger v1.4.13, slightly
patched to fix the previous issue I mentioned with the "ORDER BY" and
PostgreSQL v7.1. I intend to upgrade this system to SQL-Ledger v1.6.0 as
soon as possible, but in the meantime I'd like to share the report sent to
me by our company's accounting manager.
I have very minimal knowledge as far as accounting procedures are
concerned, so I hope those in the list who know more than me will be
patient. I'd like to get help validating the points of our accounting
manager, in the hopes that we will see if these can actually be
implemented with SQL Ledger but he just hasn't figured out how, yet.
Alternatively some of the points may be useful to the development team for
the next versions to come.
I am not giving up on SQL Ledger and will keep upgrading and pushing for
its evaluation lest someone here buy Quickbooks (ugh, but the guy's good
at Quickbooks it seems although we don't have that installed here in the
office [yet, and I hope it will stay that way]) and need me to maintain
yet more Windows computers. I hope fellow list members can help me in my
"crusade". :)
Here's the report (sometimes it looks like more of a wishlist):
- -----[ Start of Report ]-----
I. Recording
A. A/R A/P
1. Although it supports Double entry accounting it has no feature
that shows the accounting entry behind the transaction posted.
This is critical for audit trail.
2. We were not able to enter transactions with compound entries.
Without this feature it will double our accounting work.
3. VAT & Withholding tax automatic computation or recalculation.
4 Limited search function.
5. Due date recalculation.
6. Add transaction is not linked with the complete cycle of a
transaction to eliminate redundancy of accounting work. Eg. for
AR transaction, SO is linked with SI and the journal entry behind
the transaction.
7. Add transaction template can not be edited for additional field for
reporting purposes.
II. Reporting
A. Customizable reports
1. Limited customizable reports templates.
2. Additional fields for filtering report purposes.
3. Linking of SO, SI, and journal entry transaction to eliminate
redundancy.
4. Segment Reporting, & Cost center reporting???
III. Inventory
A. Inventory Tracking and Costing
1. Costing by FIFO, LIFO or average costing?
IV. Fixed asset monitoring
A. Lapsing schedule
V. Audit Trail
A. Account analysis for audit review and schedule preparation.
Comments:
The version we are evaluating basically supports bookkeeping and standard
reporting. Although I have not seen the changes in the new version, these
changes are basic accounting features in a computerized environment. We
may need a lot of time in the development before we can migrate to the
system.
- -----[ End of Report ]-----
Thanks in advance, everyone!
--> Jijo
- --
Federico Sevilla III :: ji...@le...
Network Administrator :: The Leather Collection, Inc.
GnuPG Key: <http://jijo.leathercollection.ph/jijo.gpg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7fdsw5rCBSJO3Rr4RAp6IAJoCBZXyGhUFkX/1cCBvq68ExqnZAACfbJln
HCVvbrlMqrhtQznsK/gkFS0=
=prie
-----END PGP SIGNATURE-----
|
|
From: Federico S. I. <ji...@le...> - 2001-08-18 12:27:17
|
On Fri, 17 Aug 2001 at 21:40, Ing. Antonio A. Gallardo wrote: > Thanks for your comments. Some of those features you requesteed are > implemented in the new 1.6.0 version. Would you know which ones? Anyway, I'll upgrade soon and let our accounting manager give it another spin. > Help us to develop SQL-Ledger to live out of the endless upgrade cycle > of the Microsoft environment. I wish I knew my accounting theory enough, but I don't. I'd love to pitch in. The SQL-Ledger code is clean enough to understand. The farthest I've gone was to work on that "ORDER BY" incompatibility with PostgreSQL v7.1.x. Anyway, I'll be hanging around. I won't give up, and the budget is helping me. We're tight on cash so we can't get any commercial app anyway. Hahaha. There are plusses to being in a third world country. :) --> Jijo -- Federico Sevilla III :: ji...@le... Network Administrator :: The Leather Collection, Inc. GnuPG Key: <http://jijo.leathercollection.ph/jijo.gpg> |
|
From: Jeff K. <jt...@ad...> - 2001-08-18 19:19:28
|
I need some assistance getting SQL-Ledger 1.6 to run on RH7.1 with PostgreSQL 7.1.x. I have database connection problems. I'm wondering if I need to do some sort of "GRANT ALL" on the postgres user or something. I've installed DBD::Pg and tested it successfully. There is a pgsqltest database as a result, in fact. I have (for the moment) postgres open with a blank password and listening with 'no authentication required', although I don't yet know how to tell the postgres-specific distinction between 'local connection' and localhost connection. How do I tell if postgres is listening on 5434? I easily can access postgres via webmin, for example. Database Host:localhost Port:5432 Database Administrator: postgres Password: (blank) Connect to: mypgdb (choose 'create database' results in:) Error! connectDBStart() -- connect() failed: Connection refused Likewise, I have a sql-ledger user with the following profile: Driver: Pg Host: localhost Name: mypgdb Port: 5432 User: postgres Password: (blank) (Logging in as this user results in:) Error! Database is offline; please try again later Looking at the 'Granted Priveledges" thru webmin, I see no tables having any explicitly granted priviledges. Isn't the 'postgres' user implicitly granted permission? Can anyone help me figure this out? I have to deploy this sql-ledger test ASAP. Thanks. |
|
From: Thomas G. <to...@ad...> - 2001-08-18 19:27:51
|
On Sat, 18 Aug 2001, Jeff Kowalczyk wrote:
> I need some assistance getting SQL-Ledger 1.6 to run on RH7.1 with
> PostgreSQL 7.1.x. I have database connection problems. I'm wondering if
> I need to do some sort of "GRANT ALL" on the postgres user or something.
>
> I've installed DBD::Pg and tested it successfully. There is a pgsqltest
> database as a result, in fact. I have (for the moment) postgres open
> with a blank password and listening with 'no authentication required',
> although I don't yet know how to tell the postgres-specific distinction
> between 'local connection' and localhost connection. How do I tell if
> postgres is listening on 5434? I easily can access postgres via webmin,
> for example.
Hi. Have a look in /tmp
# ls -al /tmp
See if you have a lock file (looks like .s.PGSQL.5432)
If not:
as root run:
/etc/rc.d/init.d/postgresql start
Good luck!
--------------------------------------------------------------------
SVCMC - Center for Behavioral Health
--------------------------------------------------------------------
Thomas Good tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst Phone: 718-354-5528
Residential Services Mobile: 917-282-7359
--------------------------------------------------------------------
/* Die Wahrheit Ist Irgendwo Da Draussen... */
--------------------------------------------------------------------
|
|
From: Dieter S. <dsi...@sq...> - 2001-08-18 19:36:35
|
You have to add the -i switch when you start postmaster. Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Sat, 18 Aug 2001, Jeff Kowalczyk wrote: > I need some assistance getting SQL-Ledger 1.6 to run on RH7.1 with > PostgreSQL 7.1.x. I have database connection problems. I'm wondering if > I need to do some sort of "GRANT ALL" on the postgres user or something. > > I've installed DBD::Pg and tested it successfully. There is a pgsqltest > database as a result, in fact. I have (for the moment) postgres open > with a blank password and listening with 'no authentication required', > although I don't yet know how to tell the postgres-specific distinction > between 'local connection' and localhost connection. How do I tell if > postgres is listening on 5434? I easily can access postgres via webmin, > for example. > > Database > Host:localhost Port:5432 > Database Administrator: postgres Password: (blank) > Connect to: mypgdb > (choose 'create database' results in:) > Error! connectDBStart() -- connect() failed: Connection refused > > > Likewise, I have a sql-ledger user with the following profile: > Driver: Pg Host: localhost > Name: mypgdb Port: 5432 > User: postgres Password: (blank) > (Logging in as this user results in:) > Error! Database is offline; please try again later > > Looking at the 'Granted Priveledges" thru webmin, I see no tables having > any explicitly granted priviledges. Isn't the 'postgres' user implicitly > granted permission? > > Can anyone help me figure this out? I have to deploy this sql-ledger > test ASAP. Thanks. > > > |
|
From: Jeff K. <jt...@ad...> - 2001-08-18 19:43:12
|
What is postmaster? I saw that in the FAQ, but I've never heard the word before. > You have to add the -i switch when you start postmaster. |
|
From: Jeff K. <jt...@ad...> - 2001-08-18 19:59:57
|
I see it now, postmaster is buried in the init.d script for RedHat. I have a PostgreSQL 7.1.32 installation on RH7.1, can I insert '-i' in the init.d script? My best guess where is the line: su -l postgres -s /bin/sh -c "/usr/bin/pgctl -D $PGDATA -p /ur/bin/postmaster start > /dev/null 2>&1" < /dev/null To which I tried to insert -i before and after the 'start' but that makes the startup script fail. Any suggestions? > You have to add the -i switch when you start postmaster. |
|
From: Thomas G. <to...@ad...> - 2001-08-18 20:15:46
|
On Sat, 18 Aug 2001, Jeff Kowalczyk wrote:
> I see it now, postmaster is buried in the init.d script for RedHat. I
> have a PostgreSQL 7.1.32 installation on RH7.1, can I insert '-i' in the
> init.d script?
>
> My best guess where is the line:
> su -l postgres -s /bin/sh -c "/usr/bin/pgctl -D $PGDATA -p
> /ur/bin/postmaster start > /dev/null 2>&1" < /dev/null
>
> To which I tried to insert -i before and after the 'start' but that
> makes the startup script fail.
>
> Any suggestions?
Jeff, postmaster accepts -i as an arg: postmaster -i
run: man postmaster
for more information.
But, I use Lamar's script (the one in /etc/rc.d/init.d) without
modification on RH 6.1 and RH 7.0 and it runs sql-ledger fine.
In fact...
ps ax | grep postmaster
shows:
/usr/bin/postmaster -i
--------------------------------------------------------------------
SVCMC - Center for Behavioral Health
--------------------------------------------------------------------
Thomas Good tomg@ { admin | q8 } .nrnet.org
Programmer/Analyst Phone: 718-354-5528
Residential Services Mobile: 917-282-7359
--------------------------------------------------------------------
/* Die Wahrheit Ist Irgendwo Da Draussen... */
--------------------------------------------------------------------
|
|
From: Jeff K. <jt...@ad...> - 2001-08-18 20:54:25
|
[Thomas Good] I use Lamar's script (the one in /etc/rc.d/init.d) without modification on RH 6.1 and RH 7.0 and it runs sql-ledger fine. In fact... ps ax | grep postmaster shows: /usr/bin/postmaster -i [Jeff] Thanks for that tip on ps -ax showing the arguments passed. I am using RH7.1 and PostgreSQL 7.1.2-5PGDG, installed from the RPMS. My '/etc/rc.d/init.d/postgres' script runs with the following arguments: ps ax | grep postmaster shows: /usr/bin/postmaster -D /var/lib/pgsql/data So, I guess I need to find out where in this init.d line the '-i' should be placed. su -l postgres -s /bin/sh -c "/usr/bin/pgctl -D $PGDATA -p /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null placing -i on either side of the 'start', or before the -D causes the init.d script to fail startup. Thanks for the iterative help here. This mailing list is pretty responsive. |
|
From: <ro...@su...> - 2001-08-18 21:38:12
|
"man pg_ctl" should tell you what you need to know. Note especially the references to "-o" and "postmaster.opts.default". Cheers, -- Rod http://www.sunsetsystems.com/ > [Thomas Good] I use Lamar's script (the one in /etc/rc.d/init.d) > without modification on RH 6.1 and RH 7.0 and it runs sql-ledger fine. > > In fact... > > ps ax | grep postmaster > shows: > /usr/bin/postmaster -i > > [Jeff] Thanks for that tip on ps -ax showing the arguments passed. I am > using RH7.1 and PostgreSQL 7.1.2-5PGDG, installed from the RPMS. My > '/etc/rc.d/init.d/postgres' script runs with the following arguments: > > ps ax | grep postmaster > shows: > /usr/bin/postmaster -D /var/lib/pgsql/data > > So, I guess I need to find out where in this init.d line the '-i' > should be placed. > > su -l postgres -s /bin/sh -c "/usr/bin/pgctl -D $PGDATA -p > /usr/bin/postmaster start > /dev/null 2>&1" < /dev/null > > placing -i on either side of the 'start', or before the -D causes the > init.d script to fail startup. > > Thanks for the iterative help here. This mailing list is pretty > responsive. |
|
From: Dieter S. <dsi...@sq...> - 2001-08-18 20:43:37
|
You probably have a postmaster.opts file. Add the switch to the file, you should not change startup scripts. Remember, when you upgrade Redhat again, you'll be wondering why the heck it doesn't work when it worked before. Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Sat, 18 Aug 2001, Jeff Kowalczyk wrote: > I see it now, postmaster is buried in the init.d script for RedHat. I > have a PostgreSQL 7.1.32 installation on RH7.1, can I insert '-i' in the > init.d script? > > My best guess where is the line: > su -l postgres -s /bin/sh -c "/usr/bin/pgctl -D $PGDATA -p > /ur/bin/postmaster start > /dev/null 2>&1" < /dev/null > > To which I tried to insert -i before and after the 'start' but that > makes the startup script fail. > > Any suggestions? > > > You have to add the -i switch when you start postmaster. > > > |
|
From: Jeff K. <jt...@ad...> - 2001-08-18 21:23:09
|
[Deiter] You probably have a postmaster.opts file. Add the switch to the file, you should not change startup scripts. Remember, when you upgrade Redhat again, you'll be wondering why the heck it doesn't work when it worked before. [Jeff] I agree, changing the init.d is bad. I found the postmaster.opts file in /var/lib/pgsql. However, it looks as if there's a complete and independent command line in the init.d script, does it even accede to the postmaster.opts as an override when invoked by the init.d script without any further coaxing? My initial impression is that it doesn't, since: 1) (as su postgres) I add '-i' to /var/lib/pgsql/postmaster.opts, as follows: /usr/bin/postmaster '-i' '-D' '/var/lib/pgsql/data' 2) (as su root) I then run the RH7.1 standard '/etc/rc.d/init.d/postgres restart': 3) ps -ax | grep postmaster shows: /usr/bin/postmaster -D /var/lib/pgsql/data indicating tha it ignored the .opts file. 4) and here's the kicker: Whatever is going on, it rewrites postmaster.opts to the original form! All changes are lost! This a strange startup environment, to be sure. I would attach the RH7.1 init.d/postgres script, but it's outside of mailinglist etiquette, AFAIK. |
|
From: Jeff K. <jt...@ad...> - 2001-08-19 04:29:32
|
First, off thanks to everyone who helped me hash out my PostgreSQL '-i' problems. The various postmaster.opts methods would not work under any number of syntaxes. It turned out that the way (and a simple one at that) to get postmaster listening on 5432 with my RH7.1/Pg7.1 combination was to use the postgresql.conf option "tcpip_socket=true". That accomplished the same thing as '-i'. I don't know if the .conf file is a relatively new idiom to postgres, as most of the docs don't refer to it. One for the FAQ, I guess. |
|
From: Wayne B. <wb...@co...> - 2001-08-19 05:52:19
|
Jeff, I had to add the -i flag to postmaster.opts.default to get it to work. I looked at pg_ctl and found the following: # if we are in start mode, then look for postmaster.opts.default # if we are in restart mode, then look for postmaster.opts My postmaster.opts files look like this: root@oldhome:/usr/local/pgsql/data# more postmaster.opts* :::::::::::::: postmaster.opts :::::::::::::: /usr/local/pgsql/bin/postmaster '-D' '/usr/local/pgsql/data' '-i' '-D' '/usr/local/pgsql/data' :::::::::::::: postmaster.opts.default :::::::::::::: /usr/local/pgsql/bin/postmaster '-i' '-D' '/usr/local/pgsql/data' Maybe this is worth a try. Wayne Jeff Kowalczyk wrote: > > First, off thanks to everyone who helped me hash out my PostgreSQL '-i' > problems. The various postmaster.opts methods would not work under any > number of syntaxes. > > It turned out that the way (and a simple one at that) to get postmaster > listening on 5432 with my RH7.1/Pg7.1 combination was to use the > postgresql.conf option "tcpip_socket=true". That accomplished the same > thing as '-i'. I don't know if the .conf file is a relatively new idiom > to postgres, as most of the docs don't refer to it. > > One for the FAQ, I guess. |
|
From: Thomas G. <to...@ad...> - 2001-08-19 11:16:20
|
On Sun, 19 Aug 2001, Jeff Kowalczyk wrote: > It turned out that the way (and a simple one at that) to get postmaster > listening on 5432 with my RH7.1/Pg7.1 combination was to use the > postgresql.conf option "tcpip_socket=true". That accomplished the same > thing as '-i'. I don't know if the .conf file is a relatively new idiom > to postgres, as most of the docs don't refer to it. > > One for the FAQ, I guess. Jeff, Here are two other approaches. 1) You could tweak your /etc/inittab like so: db:5432:respawn:/bin/su - postgres -c "/usr/local/pgsql/bin/postmaster -i -D/usr/local/pgsql/data >> /usr/local/pgsql/postlog 2>&1" > /dev/null Then add a line to your rc.local: rm -f /tmp/.s.PGSQL.5432 in case of unplanned shutdown (this prevents the respawn errors) 2) Alternately, use your own script: #!/bin/sh # SQL Clinic --- Version 1.0.0 # Thomas Good <www.sqlclinic.net> # ident: /usr/local/clinic/pg_start echo -n "Starting postgres service..." echo "nohup postmaster -i > /home/postgres/postgres.log 2>&1 &" | su - postgres sleep 1 pid=`pidof postmaster` echo -e "postmaster: pid [$pid] started..." The advantage of rolling your own is that: a) when you upgrade or move to a new box you take your utilities with you - and - b) I have logging enabled in both approaches (most sql-ledger errors wind up in apache's error_log but I use Pg for other things too.) These scripts assume that Pg env vars are set and that postgres' home is /home/postgres. Cheers... Oh. Almost forgot...here's a shutdown script: #!/bin/sh # ident: /usr/local/clinic/pg_stop echo -n "Stopping postgres service..." pid=`pidof postmaster` if [ "$pid" != "" ] ; then echo -n "postmaster: pid [$pid] killed." kill -TERM $pid sleep 1 fi -------------------------------------------------------------------- SVCMC - Center for Behavioral Health -------------------------------------------------------------------- Thomas Good tomg@ { admin | q8 } .nrnet.org Programmer/Analyst Phone: 718-354-5528 Residential Services Mobile: 917-282-7359 -------------------------------------------------------------------- /* Die Wahrheit Ist Irgendwo Da Draussen... */ -------------------------------------------------------------------- |