sql-ledger-users — SQL-Ledger users

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Paul T. <pt...@wa...>]

in the /sql dir there are sripts named Pg-upgrade-2.0.8-2.2.0.sql etcetera
Start on the one you have and work up to actual version: bos is now part of
the family ;-)

2008/6/22 Stuart Luppescu <sl...@cc...>:

> On 日, 2008-06-15 at 00:33 +0200, Paul Tammes wrote:
> > Upgrading and restoring at the same time?  Seems a bit tricky to begin
> > with.
> >
> > If all else fails first restore to same version then do upgrades
> > later. But maybe this helps:
> >
> > Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts
> > before letting postgres or SQL-Ledger have a second go?
> > If not i strongly suggest you do that, saved my ass in the past
> > getting from a blown 2.2 to a new 2.4 iirc..
>
> I downgraded back to 2.6.27, restored from the backup, and everything
> was fine. Then I tried upgrading to 2.8.1 and got the same message as
> before:
> Error!
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: relation "cargo" already exists
>
> I tried over and over, but I keep getting the same message. This is
> getting frustrating.
>
> Paul, where do I get those upgrade scripts you mention?
>
> --
> Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> University of Chicago (^_^)/ CCSR
> 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> Denver, n.:  A smallish city located just below
>  the `O' in Colorado.
>
>
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Rolf S. <in...@to...>]

It seems your database already contains a table "cargo". You should find 
it somewhere in your dump file.
1) Make a backup.
2) Insert at the beginning of sql/Pg-upgrade-2.7.0-2.7.5.sql:

drop table if exists cargo;

3) Try again to upgrade.

Stuart Luppescu schrieb:
> Error!
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: relation "cargo" already exists

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

On 日, 2008-06-15 at 00:33 +0200, Paul Tammes wrote:
> Upgrading and restoring at the same time?  Seems a bit tricky to begin
> with.
> 
> If all else fails first restore to same version then do upgrades
> later. But maybe this helps:
> 
> Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts
> before letting postgres or SQL-Ledger have a second go?
> If not i strongly suggest you do that, saved my ass in the past
> getting from a blown 2.2 to a new 2.4 iirc..

I downgraded back to 2.6.27, restored from the backup, and everything
was fine. Then I tried upgrading to 2.8.1 and got the same message as
before:
Error!
create table cargo (id int not null, trans_id int not null, package
text, netweight float4, grossweight float4, volume float4)
ERROR: relation "cargo" already exists

I tried over and over, but I keep getting the same message. This is
getting frustrating.

Paul, where do I get those upgrade scripts you mention?

-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
Denver, n.:  A smallish city located just below
 the `O' in Colorado. 
 
 
 

Re: [SL] Server Error After Backend Upgrade -- FIXED!

[Rich S. <rsh...@ap...>]

On Thu, 19 Jun 2008, Paul Tammes wrote:

> Are you sure your Postgresql db is running correctly? I upgraded hardware
> and changed to opensuse 11.0 beta in the same run. On starting postgresql,
> opensuse gave the warning that the DB would tremain using 8.1 iso 8.3
> version of Postgresql untill I had updated all db related files. Something
> similar might be going on with two versions of Pg.pm but without the nice
> warnings?

Paul,

   When I looked at /var/log/apache/error_log I saw that the problem was most
likely with the DBD::Pg version; the installed one was too old. One of the
local perl mongers verified that.

   My first attempts to upgrade using the CPAN client failed. Today, I
removed the Pg.pm that was apparently broken and forced a re-installation.
This time it worked.

   Since I can now log in and use SL, this thread can be closed with success.
Thank you very much for your input, you are correct that it was the Pg.pm
module that needed to be updated.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Paul T. <pt...@wa...>]

Are you sure your Postgresql db is running correctly?
I upgraded hardware and changed to opensuse 11.0 beta in the same run.
On starting postgresql, opensuse gave the warning that the DB would tremain
using 8.1 iso 8.3 version of Postgresql untill I had updated all db related
files. Something similar might be going on with two versions of Pg.pm but
without the nice warnings?


2008/6/18 Rich Shepard <rsh...@ap...>:

> On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:
>
> > My bad; I would check the new file,
> > /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.
>
> Wallace,
>
>   I think the problem is related to having two versions of Pg.pm installed.
> Apparently, CPAM does not upgrade and older version by replacing it with
> the
> newer version, but leaves both versions, and in different directories. One
> of the local perl mongers is looking at the situation.
>
> Thanks,
>
> Rich
>
> --
> Richard B. Shepard, Ph.D.               |  Integrity            Credibility
> Applied Ecosystem Services, Inc.        |            Innovation
> <http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax:
> 503-667-8863
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:

> My bad; I would check the new file,
> /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.

Wallace,

   I think the problem is related to having two versions of Pg.pm installed.
Apparently, CPAM does not upgrade and older version by replacing it with the
newer version, but leaves both versions, and in different directories. One
of the local perl mongers is looking at the situation.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:

> My bad; I would check the new file,
> /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.

Wallace,

   That's not been changed since 2006-09-01 21:39.

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Wallace R. C. <wrc...@gm...>]

On Wed, Jun 18, 2008 at 1:35 PM, Rich Shepard <rsh...@ap...> wrote:
> On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:
>
>> I've seen this error caused by something as simple as an M$-WinDoze(tm)
>> text file (with carriage-return+linefeed sequences to terminate a line) on
>> a Un*x (or Un*x-like, i.e., Linux) system, which expects only linefeeds
>> terminating lines.
>
> Wallace,
>
> That could be, but we've not done Microsoft here for more than a decade.
> The only change here has been to the db back end, and the error seems to
> refer to the perl DBD::Pg module.

My bad; I would check the new file,
/usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm, instead.

-- 
Best Regards,
Wallace

Re: [SL] Server Error After Backend Upgrade

[Stuart L. <sl...@cc...>]

On 水, 2008-06-18 at 13:23 -0700, Wallace Roberts Consulting wrote:
> To force the correct (Un*x) format of a non-Un*x file (on your Un*x
> system), use the following command in VIM:
> 
>     :set ff=unix
> 
> Then save the file, & you're done.

Nice. You can also use the dos2unix utility, or load the file into emacs
and do C-x RET f and then enter undecided-unix. Or in emacs M-x
set-buffer-file-coding-system undecided-unix.
-- 
Stuart Luppescu -=- slu .at. ccsr.uchicago.edu        
University of Chicago -=- CCSR 
才文と智奈美の父 -=-    Kernel 2.6.24-gentoo-r8                
Distress, n.:  A disease incurred by exposure to
 the prosperity of a friend.   -- Ambrose Bierce,
 "The Devil's Dictionary" 
 
 

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Wallace Roberts Consulting wrote:

> I've seen this error caused by something as simple as an M$-WinDoze(tm)
> text file (with carriage-return+linefeed sequences to terminate a line) on
> a Un*x (or Un*x-like, i.e., Linux) system, which expects only linefeeds
> terminating lines.

Wallace,

   That could be, but we've not done Microsoft here for more than a decade.
The only change here has been to the db back end, and the error seems to
refer to the perl DBD::Pg module.

> To force the correct (Un*x) format of a non-Un*x file (on your Un*x
> system), use the following command in VIM:

   I've used dos2unix, but that's not appropriate here.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

Re: [SL] Server Error After Backend Upgrade

[Wallace R. C. <wrc...@gm...>]

On Wed, Jun 18, 2008 at 11:43 AM, Rich Shepard <rsh...@ap...> wrote:
...
>  at SL/User.pm line 103
> Compilation failed in require at /usr/local/sql-ledger/login.pl line 85.
> [Wed Jun 18 11:39:57 2008] [error] [client 127.0.0.1] Premature end of
> script headers: /usr/local/sql-ledger/login.pl

I've seen this error caused by something as simple as an
M$-WinDoze(tm) text file (with carriage-return+linefeed sequences to
terminate a line) on a Un*x (or Un*x-like, i.e., Linux) system, which
expects only linefeeds terminating lines.

If you edit your login.pl file with VIM (VI-iMproved), see what kind
of format the file has.  For example, when I edit a Un*x file, the
status line on the bottom of the screen will indicate so:

    "blah.xml" [unix] [readonly]  445L, 17033C   92,6-41    18%

To force the correct (Un*x) format of a non-Un*x file (on your Un*x
system), use the following command in VIM:

    :set ff=unix

Then save the file, & you're done.
-- 
Best Regards,
Wallace

Re: [SL] Trend analysis

[C. D. H. <du...@du...>]

Sorry, I've been out of the loop for awhile.  Send me a message off list 
and I'll send you a copy of the script.

Dunc

Ed W wrote:
> C. Duncan Hudson wrote:
>   
>> What kind of trends are you looking for?  For sales analysis I wrote a 
>> little Perl script that is cron'd to run on the 5th day of each month 
>> (gives me a couple of days to fix any month end issues).  The script 
>> summarizes each sales person's sales and receivables for the month.  It 
>> also provides a delta of the month over the previous month and the month 
>> over the same month one year ago.  Finally, it builds a nice little 
>> (electric company bill style) 13 month bar graph.  The script then 
>> emails the personalized report to the salesperson and their manager.
>>
>> For inventory analysis I have a Perl script that  is cron'd hourly.  My 
>> reorder points (minimum), and EOQ are recalculated each time the script 
>> runs.  When ever any of the stocked items falls below their minimum an 
>> email is fired off to the person who does the parts ordering.  The 
>> script also does Pareto Analysis (ABC) and labels each item as such 
>> along with its percentage of both sales and revenue.
>>   
>>     
>
> Can we see the scripts?
>
> Ed W
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>   

Re: [SL] Trend analysis

[C. D. H. <du...@du...>]

"Hello pot?  This is kettle..."  One might look through this list and 
say the same to you!

Dieter Simader wrote:
> I asked a simple question and you hurle insults.
>
> Is it so hard to provide a reasonable answer rather than you getting all 
> uptight about feeling rejected.
>
>
> On Fri, 6 Jun 2008, Ed W wrote:
>
>   
>> Dieter Simader wrote:
>>     
>>> On Fri, 6 Jun 2008, Ed W wrote:
>>>
>>>
>>> You are still here, why?
>>>
>>> http://sourceforge.net/mailarchive/forum.php?thread_name=484435EA.7000309%40wildgooses.com&forum_name=ledger-smb-devel
>>>
>>>       
>> I am on SL 2.6.27 (which I have "outgrown").  I am trying to decide
>> where to go next
>>
>> You have given me one more reason to reject continuing with SL - I need
>> to find a system with good backup and support and your comments often
>> "suggest" that I would not find it with SL - I get a strong sense that
>> you would be happy to take my money upfront, but not be particularly
>> forthcoming afterwards - please don't be insulted if you mean otherwise,
>> I am only voicing my concerns
>>
>> For those watching at home I have previously (ok, minorly) supported SL
>> to the tune of buying a single year of updates of "the manual".  I
>> lapsed for various reasons but until 10 minutes ago restarting support
>> was a serious possibility.  I have a total budget of around $20-40K for
>> all the changes I need made to get whatever solution I pick to the point
>> it works well for my needs.
>>
>> I get an increasingly strong sense that I'm not wanted by the SL
>> community though...
>>
>> Good luck to you in any case - you have created a very compelling bit of
>> software and deserve to profit from it - I am personally distressed by
>> the serious problems I keep finding with it's adding up (fixable though
>> I'm sure, which is why I'm still here), however, it has a very good GUI
>> and a good feature set for many small businesses.  It's just a shame
>> that  you seem to chase away some of your customers...
>>
>>
>> Regards
>>
>> Ed W
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>>     
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>   

Re: [SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

On Wed, 18 Jun 2008, Rich Shepard wrote:

>   Do these messages mean that the installed DBD::Pg module does not work
> with the most recent version of Postgres, and that I need to update that
> module?

   I just upgraded DBD::Pg, and now have different errors:

[Wed Jun 18 11:39:51 2008] [notice] Accept mutex: sysvsem (Default: sysvsem)
install_driver(Pg) failed: DBD::Pg object version undef does not match
bootstrap
  parameter 2.8.1 at /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm line 253.
Compilation failed in require at (eval 10) line 3.

  at SL/User.pm line 103
Compilation failed in require at /usr/local/sql-ledger/login.pl line 85.
[Wed Jun 18 11:39:57 2008] [error] [client 127.0.0.1] Premature end of
script he
aders: /usr/local/sql-ledger/login.pl

   My knowledge of Perl hovers around zero, so I'd really appreciate some
help on how to fix the problem.

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

[SL] Server Error After Backend Upgrade

[Rich S. <rsh...@ap...>]

   I just upgraded the PostgreSQL backend from -8.1.4 to -8.3.3, and I
restored the data to the new version. When I try to invoke SL I get a server
error.

   The relevant lines in /var/log/apache/error_log are:

[Wed Jun 18 10:52:44 2008] [error] [client 127.0.0.1] Premature end of
script headers: /usr/local/sql-ledger/login.pl
install_driver(Pg) failed: Can't load '/usr/lib/perl5/site_perl/5.8.8/i486-linux
/auto/DBD/Pg/Pg.so' for module DBD::Pg: libpq.so.4: cannot open shared
object file: No such file or directory at /usr/lib/perl5/5.8.8/i486-linux/DynaLoader.pm 
line 230. at (eval 10) line 3 Compilation failed in require at (eval 10) line 3.
Perhaps a required shared library or dll isn't installed where expected at SL/User.pm line 103
Compilation failed in require at /usr/local/sql-ledger/login.pl line 85.
[Wed Jun 18 10:58:19 2008] [error] [client 127.0.0.1] Premature end of
script headers: /usr/local/sql-ledger/login.pl

   Do these messages mean that the installed DBD::Pg module does not work
with the most recent version of Postgres, and that I need to update that
module? Or, is there something else going on here?

Thanks,

Rich

-- 
Richard B. Shepard, Ph.D.               |  Integrity            Credibility
Applied Ecosystem Services, Inc.        |            Innovation
<http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863

[SL] Error SL/Form.pl

[Adrian <adr...@ie...>]

While printing a purchase order I get the following:



Bizarre copy of UNKNOWN in sassign at SL/Form.pm line 984.

Item 	Number 	Description 	Qt'y 	  	Price 	% 	Amount
1. 	CAD240 	Battery, hi-cap, AA tagged 	2 		5.50 		11.00
31/01/2009. 	mp9012 	MP3 player black 	1 		129.50 		129.50
01/01/2009. 	NEOCD30 	Fountek NeoCD3.0 ribbon tweeter pair 	1 		149.00 		149.00

Note the item numbers after the first have dates and not item numbers, and that date is also bizarre.

A similar in printing from Accounts Receivable

I am using SQL-Ledger 2.8.14.

I have recently upgraded the postgres.

Adrian

Re: [SL] PDA input?

[Dr E. L. <el...@li...>]

I am about to get an EEE 901 for this and similar
purposes :-)-O.

el

on 6/14/08 6:40 PM Michael Hasse said the following:
 > That's a possible option, but we're trying to get down to something a
 > lot smaller and tougher, like a ruggedized PDA or something.
 >     However, one item in your email below catches my eye - it sounds
 > like a copy of SL can be loaded independently of the "main" system
 > and then the datasets merged/sync'd periodically...?
 >
 >
 > Thanks!
 >
 > Michael
 >
 > On Jun 14, 2008, at 1:49 AM, Paul Tammes wrote:
 >
 >> How about an Asus EEE pc or something likewise?
 >> Just install SQL ledger on the EEE, hit the road and sync when
 >> needed ;-)
 >

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Paul T. <pt...@wa...>]

Upgrading and restoring at the same time?  Seems a bit tricky to begin with.

If all else fails first restore to same version then do upgrades later. But
maybe this helps:

Did you use the upgrade-2.x.x-databasename_2.x.y-databasename scripts before
letting postgres or SQL-Ledger have a second go?
If not i strongly suggest you do that, saved my ass in the past getting from
a blown 2.2 to a new 2.4 iirc..


2008/6/14 Michael Hasse <mh...@it...>:

> Not a complete answer but we've seen the TOC error after upgrades as
> some of the rights get reset and the user the dump is executing under
> doesn't have access.
>
>
> Thanks,
>
> Michael
>
> On Jun 14, 2008, at 11:14 AM, Stuart Luppescu wrote:
>
> > On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
> >> I've been putting off the upgrade as long as I could, but I
> >> finally gave
> >> it a go. However, when I log in after following the instructions,
> >> I get
> >> this error:
> >>
> >> Error!
> >>
> >> drop trigger del_recurring ON oe
> >> ERROR: trigger "del_recurring" for table "oe" does not exist
> >
> > Well, I just tried again and it worked (after I deleted the nologin
> > file). But then I found that my nightly backups using pg_dump and
> > restores to a mirror system stopped working about a week ago. I'm
> > getting these messages:
> >
> > pg_restore: [tar archiver] could not open TOC file for input: No such
> > file or directory
> >
> > The line that triggers this message is:
> > pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup
> >
> > The funny thing is that the backup file suddenly went from 4.1MB in
> > size
> > to 9.3MB on the day it stopped working. I had upgraded postgres from
> > 8.0.13 to 8.0.15 a few days previous, and then we had a power failure
> > and when the machine rebooted, these problems started.
> >
> > So, since my mirror was a week out of date, I got a backup file from
> > System -> Backup -> Save to file, and restored that to my mirror
> > system.
> > Then when I logged in I got this error message:
> >
> > Upgrading to Version 2.8.15 ...
> > Error!
> > create table cargo (id int not null, trans_id int not null, package
> > text, netweight float4, grossweight float4, volume float4)
> > ERROR: relation "cargo" already exists
> >
> > I REALLY need to get this working again. Any help will be greatly
> > appreciated.
> >
> > --
> > Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> > University of Chicago (^_^)/ CCSR
> > 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> > Respect is a rational process   -- McCoy, "The
> >  Galileo Seven", stardate 2822.3
> >
> >
> >
> >
> >
> > ----------------------------------------------------------------------
> > ---
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > _______________________________________________
> > sql-ledger-users mailing list
> > sql...@li...
> > https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Michael H. <mh...@it...>]

Not a complete answer but we've seen the TOC error after upgrades as  
some of the rights get reset and the user the dump is executing under  
doesn't have access.


Thanks,

Michael

On Jun 14, 2008, at 11:14 AM, Stuart Luppescu wrote:

> On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
>> I've been putting off the upgrade as long as I could, but I  
>> finally gave
>> it a go. However, when I log in after following the instructions,  
>> I get
>> this error:
>>
>> Error!
>>
>> drop trigger del_recurring ON oe
>> ERROR: trigger "del_recurring" for table "oe" does not exist
>
> Well, I just tried again and it worked (after I deleted the nologin
> file). But then I found that my nightly backups using pg_dump and
> restores to a mirror system stopped working about a week ago. I'm
> getting these messages:
>
> pg_restore: [tar archiver] could not open TOC file for input: No such
> file or directory
>
> The line that triggers this message is:
> pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup
>
> The funny thing is that the backup file suddenly went from 4.1MB in  
> size
> to 9.3MB on the day it stopped working. I had upgraded postgres from
> 8.0.13 to 8.0.15 a few days previous, and then we had a power failure
> and when the machine rebooted, these problems started.
>
> So, since my mirror was a week out of date, I got a backup file from
> System -> Backup -> Save to file, and restored that to my mirror  
> system.
> Then when I logged in I got this error message:
>
> Upgrading to Version 2.8.15 ...
> Error!
> create table cargo (id int not null, trans_id int not null, package
> text, netweight float4, grossweight float4, volume float4)
> ERROR: relation "cargo" already exists
>
> I REALLY need to get this working again. Any help will be greatly
> appreciated.
>
> -- 
> Stuart Luppescu -=- s-luppescu .at. uchicago.edu
> University of Chicago (^_^)/ CCSR
> 才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
> Respect is a rational process   -- McCoy, "The
>  Galileo Seven", stardate 2822.3
>
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users

Re: [SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

On 土, 2008-06-14 at 12:09 -0500, Stuart Luppescu wrote:
> I've been putting off the upgrade as long as I could, but I finally gave
> it a go. However, when I log in after following the instructions, I get
> this error:
> 
> Error!
> 
> drop trigger del_recurring ON oe
> ERROR: trigger "del_recurring" for table "oe" does not exist

Well, I just tried again and it worked (after I deleted the nologin
file). But then I found that my nightly backups using pg_dump and
restores to a mirror system stopped working about a week ago. I'm
getting these messages:

pg_restore: [tar archiver] could not open TOC file for input: No such
file or directory

The line that triggers this message is:
pg_restore -c -U sql-ledger -d dbname -F t postgresql_database-backup

The funny thing is that the backup file suddenly went from 4.1MB in size
to 9.3MB on the day it stopped working. I had upgraded postgres from
8.0.13 to 8.0.15 a few days previous, and then we had a power failure
and when the machine rebooted, these problems started.

So, since my mirror was a week out of date, I got a backup file from
System -> Backup -> Save to file, and restored that to my mirror system.
Then when I logged in I got this error message:

Upgrading to Version 2.8.15 ... 
Error!
create table cargo (id int not null, trans_id int not null, package
text, netweight float4, grossweight float4, volume float4)
ERROR: relation "cargo" already exists

I REALLY need to get this working again. Any help will be greatly
appreciated.

-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
Respect is a rational process   -- McCoy, "The
 Galileo Seven", stardate 2822.3 
 
 
 

Re: [SL] PDA input?

[Michael H. <mh...@it...>]

That's a possible option, but we're trying to get down to something a  
lot smaller and tougher, like a ruggedized PDA or something.
    However, one item in your email below catches my eye - it sounds  
like a copy of SL can be loaded independently of the "main" system  
and then the datasets merged/sync'd periodically...?


Thanks!

Michael

On Jun 14, 2008, at 1:49 AM, Paul Tammes wrote:

> How about an Asus EEE pc or something likewise?
> Just install SQL ledger on the EEE, hit the road and sync when  
> needed ;-)
>
> 2008/6/14 Michael Hasse <mh...@it...>:
>
>> Anybody have SL hooked up to any kind of external timecard input
>> device?  Specifically a PDA or similar handheld device - doesn't have
>> to be real-time, but where workorders could be pulled up and notes/
>> time/whatever punched in while on the road and either directly
>> connected to SL via wireless network or dumped into it at the end of
>> the day?
>>
>>
>> Thanks!
>>
>> Michael
>>
>> --------------------------------------------------------------------- 
>> ----
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>>
> ---------------------------------------------------------------------- 
> ---
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users

[SL] 2.6.22 -> 2.8.15 upgrade error

[Stuart L. <sl...@cc...>]

I've been putting off the upgrade as long as I could, but I finally gave
it a go. However, when I log in after following the instructions, I get
this error:

Error!

drop trigger del_recurring ON oe
ERROR: trigger "del_recurring" for table "oe" does not exist

and now when I try to log in it tells me Login disabled. Some help would
be greatly appreciated.
-- 
Stuart Luppescu -=- s-luppescu .at. uchicago.edu        
University of Chicago (^_^)/ CCSR 
才文と智奈美の父 -=-=- Kernel 2.6.23-gentoo-r
Are we not men? 
 
 
 
 

Re: [SL] PDA input?

[Paul T. <pt...@wa...>]

How about an Asus EEE pc or something likewise?
Just install SQL ledger on the EEE, hit the road and sync when needed ;-)

2008/6/14 Michael Hasse <mh...@it...>:

> Anybody have SL hooked up to any kind of external timecard input
> device?  Specifically a PDA or similar handheld device - doesn't have
> to be real-time, but where workorders could be pulled up and notes/
> time/whatever punched in while on the road and either directly
> connected to SL via wireless network or dumped into it at the end of
> the day?
>
>
> Thanks!
>
> Michael
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>

[SL] PDA input?

[Michael H. <mh...@it...>]

Anybody have SL hooked up to any kind of external timecard input  
device?  Specifically a PDA or similar handheld device - doesn't have  
to be real-time, but where workorders could be pulled up and notes/ 
time/whatever punched in while on the road and either directly  
connected to SL via wireless network or dumped into it at the end of  
the day?


Thanks!

Michael

[SL] Graphs in sql-ledger (was Trend analysis)

[Armaghan S. <sa...@le...>]

A script to build graphs in sql-ledger is available at
wiki.ledger123.com. Let me know any issues/suggestions.

Regards

-- 
* Purpose-built SQL-Ledger Hosting. Free trial.
* SQL-Ledger VMware Appliance. Free download.
http://www.ledger123.com/

--