sql-ledger-users

[SQL-Ledger-users] unsubscribe

[<drg...@ic...>]

On Thu, 19 April 2001, Richard Eicher II wrote:

> 
> When I try to log in I get:
> Error!
> 
> DBI::errstr
> 
> The error_log shows:
> 
> DBD::Pg::st execute failed: ERROR:  chart:
> Permission denied. at
> /var/www/html/sql-ledger/login.cgi line 80.
> 
> Anyone run into this problem?
> 
> Thank you for your time,
> Rick
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/

Gary Danko - President
Dynamic Resources Group, Inc.
gd...@dr...
ICQ#38631323
-------------
Get your FREE Virtual Office Suite at:
http://www.drgworld.com/x/id/1000


-------------------------------------------------------------
Sign up for ICQmail at http://www.icq.com/icqmail/signup.html

[SL] unsubscribe

[David A. s. <da...@sy...>]

On 11-Aug-08, at 1:09 PM, sql-ledger-users- 
re...@li... wrote:

> Send sql-ledger-users mailing list submissions to
> 	sql...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> or, via email, send a message with subject or body 'help' to
> 	sql...@li...
>
> You can reach the person managing the list at
> 	sql...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of sql-ledger-users digest..."
>
>
> Today's Topics:
>
>   1. Re: Apache error running summary reports - reality checking
>      script? (Michael Hasse)
>   2. Can't send email (Danita Zanre)
>   3. Re: Error SL/Form.pl (Giedrius)
>   4. Re: Can't send email (Danita Zanre)
>   5. Re: Apache error running summary reports - reality checking
>      script? (Michael Hasse)
>   6. postgresql 8.3 (david)
>   7. Re: postgresql 8.3 (Michael Hasse)
>   8. Re: postgresql 8.3 (la...@cl...)
>   9. Re: postgresql 8.3 (Paul Tammes)
>  10. Re: postgresql 8.3 (Michael Hasse)
>  11. Re: postgresql 8.3 (la...@cl...)
>  12. Re: postgresql 8.3 (Michael Hasse)
>  13. Re: Sales Invoice Question (Colin Manning)
>  14. Re: Sales Invoice Question (Michael Hasse)
>  15. Error after moving sql-ledger to a new server (Munroe Sollog)
>  16. problem emailing invoices (Munroe Sollog)
>  17. Re: problem emailing invoices (Paul Tammes)
>  18. Re: problem emailing invoices (Bob Miller)
>  19. Re: problem emailing invoices (Munroe Sollog)
>  20. Re: problem emailing invoices (Bob Miller)
>  21. Re: problem emailing invoices (Munroe Sollog)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 21 Jul 2008 10:42:45 -0700
> From: Michael Hasse <mh...@it...>
> Subject: Re: [SL] Apache error running summary reports - reality
> 	checking	script?
> To: sql...@li...
> Message-ID: <3FA...@it...>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> All valid points except that "top" shows CPU/RAM to be just fine
> while the report is running, as is disk/swap.
>    This is an older machine, our last non-virtual system, actually,
> so maybe we'll just go ahead and do the VM migration and see what
> happens.
>
>
> Thanks,
>
> Michael
>
> On Jul 21, 2008, at 8:59 AM, Paul Tammes wrote:
>
>> Seeing FC4 where 9 is out, postgresql 7.4 where 8.x is out, could
>> it be the
>> hardware is old as well?
>> I know, if it ain't broke and all that ;-)
>>
>> If the hardware is not up to speed for a larger number of months,
>> memory
>> overflow combined with swapping to (slow/old/olmost dead?) Harddisk
>> comes to
>> mind. The change in response between say an AMD Duron 800 and AMD
>> 4450e
>> dualcore is stunning.
>> Both el cheapo cpu but frome different era's alltogether: in
>> hardware 8
>> years is a lifetime and a halve.
>> Nice part: the power consumption of some modern cpu's like 4450e
>> ore dulcore
>> intels is stunningly lower.
>> So that kind of investment earns itself in a few years time as well.
>>
>> (If that is too much of an investment, try adding some extra memory
>> to the
>> old box.
>> SD-ram is still available in some antique shops, or second hand on
>> computer
>> user club trade fairs.
>> DDR (sec) is more readilly available, and other than SD-ram (which
>> is rare,
>> therefore expensive) pretty cheap as well
>>
>> Hth
>>
>> 2008/7/21 Michael Hasse <mh...@it...>:
>>
>>> Further testing shows that it is indeed something timing out.  The
>>> reason the test company report ran okay was because there were  
>>> hardly
>>> any records.  I am also able to run the problem reports okay  
>>> provided
>>> I choose only a month or two range.  Having run the reports for
>>> successive months of the entire year with no problems we can at  
>>> least
>>> get the taxes taken care of, (whew! :), and short of some bizarre
>>> boundary error this should prove that the data is okay.
>>>
>>>   But the question remains of what exactly it is that is timing
>>> out...?
>>>
>>>   In the process of testing this it looks like we actually get any
>>> of a variety of errors, some of them pretty generic, e.g. plain old
>>> Apache "Internal server error".
>>>   (William's suggestions earlier unfortunately did not pan out.)
>>>
>>>   This is an FC4 box running:
>>>       Apache 2.0.54 w/mod_perl 2.0.1
>>>       Postgresql 7.4.13
>>>       Perl 5.8.6
>>>
>>> Any ideas?
>>>
>>>
>>> Thanks!
>>>
>>> Michael
>>>
>>>
>>> ================================
>>> Based on the advice to check dates I've just been through every date
>>> value of every record of every table, and I found a couple of bogus
>>> dates, (you'd think bounds checking would catch '08-27-0200'), and
>>> fixed them, but still no go.
>>>    I also checked to see if maybe the version upgrade had missed a
>>> file due to permissions or something but all the .pl files are the
>>> same date and perms, (except setup.pl is a few days newer but that's
>>> to be expected and shouldn't matter).
>>>    What other things should we be checking?
>>>    Mismatches between invoices and line items, (e.g. line items
>>> without invoices)?
>>>
>>> <rant>
>>>    I'm really surprised there are no scripts already written for
>>> this.  I actually was a rocket scientist, ahem, database programmer,
>>> in a past life and every project I ever worked on had an "admin
>>> toolkit" by the end of it with various queries to be sure nothing
>>> bizarre had slipped through the cracks.  This wasn't intentional,  
>>> but
>>> all db programmers end up doing some "pre-QA" of their own and the
>>> scripts just grow naturally from that.
>>> </rant>
>>>
>>>    Anyway, again, suggestions would be greatly appreciated from
>>> anyone who has dealt with anything like this before...?
>>>
>>>
>>> Thanks!!!!
>>>
>>> Michael
>>>
>>>
>>>
>>> On Jul 3, 2008, at 4:06 AM, ja...@in... wrote:
>>>
>>>> A simple sanity check that I wish I had time to implement is to
>>>> regularly (cron job) :
>>>> Check each company in the database and hunt for any transactions
>>>> with illogical (ie stupid) dates
>>>> such as 07/03/2080 (transposed year digits)
>>>> Send informative email to user who entered the offending
>>>> transaction, and copy to sysadmin.
>>>> Still hoping Dieter might implement something sensible in company
>>>> defaults to solve this simple problem.
>>>> Been mentioned before.
>>>> Very interested in any other sanity checks.
>>>> DJ
>>>> On Thu 03/07/08  3:21 PM , Michael Hasse mh...@it... sent:
>>>> Months later, I'm getting back to this, (prodded by tax
>>>> deadlines of
>>>>
>>>> course!  :)
>>>>     I did check the timeout directive and raised it to some
>>>> ridiculous level to no avail, (and same duration of wait so I don't
>>>>
>>>> think that's it).
>>>>     Also don't think it's a record count issue as it was working
>>>> fine
>>>> right up a month or two before the upgrade and we don't do THAT
>>>> much
>>>>
>>>> business.
>>>>     I also opened a terminal session to the host server and watched
>>>>
>>>> the stats as it was running and there were no issues with
>>>> memory/swap/
>>>> etc running out or anything like that.
>>>>     Somebody suggested checking another company in the system,
>>>> (good
>>>>
>>>> idea, my apologies for not doing that before posting!  Brain
>>>> fade...).
>>>>     Unfortunately that company works just fine so I have to assume
>>>> at
>>>> this point that I have a corrupt record somewhere/somehow.
>>>>     So now the question is - are there any sort of scripts that can
>>>>
>>>> be run to do a sanity check?  Has anybody had to deal with bad
>>>> records and might have some tips to save a few hours of poring over
>>>>
>>>> the DB structure?
>>>> Thanks!!!!!!!!!!!!
>>>> Michael
>>>> On Jan 8, 2008, at 6:01 AM, William McKee wrote:
>>>>> On Mon, Jan 07, 2008 at 09:34:39PM -0800, Michael Hasse wrote:
>>>>>> Just an update on this.  Permissions are all fine and the reports
>>>> run
>>>>>> with no problems in our test company.  Reading up a bit on the
>>>> errors
>>>>>> it looks like a simple timeout problem where Apache is giving up
>>>> on
>>>>>> the script before it finishes due to the amount of data we have
>>>>>> slowing the script down.  (System resources are okay so we're not
>>>>
>>>>>> running out of memory or anything).
>>>>>
>>>>> Interesting, I hadn't considered timeout error causing that
>>>> message.
>>>>>
>>>>>
>>>>>>    Suggestions/advice are welcome and we'll keep plugging away
>>>> at it
>>>>>> and post back if we figure it out.
>>>>>
>>>>> Have you checked out the TimeOut directive[1]? I've seen some
>>>> people
>>>>> comment the TimeOut does not affect CGI scripts, but Apache
>>>> security
>>>>> tips[2] say the following:
>>>>>
>>>>> "As TimeOut is currently used for several different operations,
>>>>
>>>>> setting
>>>>> it to a low value introduces problems with long running CGI
>>>> scripts."
>>>>>
>>>>> I've seen others suggest using FastCGI. Keep us posted on your
>>>>> progress.
>>>>>
>>>>>
>>>>> Good luck,
>>>>> William
>>>>>
>>>> --------------------------------------------------------------------
>>>> --
>>>> ---
>>>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>>>> Studies have shown that voting for your favorite open source
>>>> project,
>>>> along with a healthy diet, reduces your potential for chronic
>>>> lameness
>>>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>>
>>> ---------------------------------------------------------------------
>>> ---
>>> -
>>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>>> Studies have shown that voting for your favorite open source  
>>> project,
>>> along with a healthy diet, reduces your potential for chronic
>>> lameness
>>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>> ---------------------------------------------------------------------
>>> ----
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win
>>> great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in
>>> the world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 21 Jul 2008 16:57:11 -0600
> From: "Danita Zanre" <da...@ca...>
> Subject: [SL] Can't send email
> To: <sql...@li...>
> Message-ID: <488...@ec...>
> Content-Type: text/plain; charset=US-ASCII
>
> So, my SQL-Ledger server has been working pretty well for a couple of
> years.  Just today i tried to send a quotation, and I get this in my
> postfix log:
>
> fatal: no login name found for user ID 30
>
> This just started happening.  I sent invoices out on July 11 with no
> problems.
>
> Any idea what's causing this all of a sudden?
>
> Thanks.
>
> Danita
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Jul 2008 11:38:37 +0300
> From: Giedrius <zl...@nk...>
> Subject: Re: [SL] Error SL/Form.pl
> To: sql...@li...
> Message-ID: <200...@nk...>
> Content-Type: text/plain; charset=US-ASCII
>
> On Tue, 15 Jul 2008 07:44:31 -0700
> Bob Miller <bo...@co...> wrote:
>
>> Giedrius:
>> Check here, the top post:
>> http://abacus.sql-ledger.com/userforum/forum.php
>>
> I installed perl 5.8.8 from source, but without success.
> Additionally, the new problem appeared - while posting a sales order I
> get the following:
>
> Error!
>
> Can't locate version/vxs.pm in @INC (@INC
> contains: /usr/local/lib/perl5/5.8.8/i686-linux /usr/local/lib/ 
> perl5/5.8.8 /usr/local/lib/perl5/site_perl/5.8.8/i686-linux /usr/ 
> local/lib/perl5/site_perl/5.8.8 /usr/local/lib/perl5/site_perl .)
> at (eval 11) line 2.
>
> Thanks in advance,
>
> -- 
> Giedrius
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Jul 2008 06:51:33 -0600
> From: "Danita Zanre" <da...@ca...>
> Subject: Re: [SL] Can't send email
> To: <sql...@li...>
> Message-ID: <488...@ec...>
> Content-Type: text/plain; charset=US-ASCII
>
> Actually, this was on a LUM enabled OES server, and something was up
> with LDAP - it's all fixed now!
>
> Thanks anyway!
>
> Danita
>
>
>>>> "Danita Zanre" <da...@ca...> 7/21/2008 4:57 PM >>>
> So, my SQL-Ledger server has been working pretty well for a couple of
> years.  Just today i tried to send a quotation, and I get this in my
> postfix log:
>
> fatal: no login name found for user ID 30
>
> This just started happening.  I sent invoices out on July 11 with no
> problems.
>
> Any idea what's causing this all of a sudden?
>
> Thanks.
>
> Danita
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 22 Jul 2008 10:31:19 -0700
> From: Michael Hasse <mh...@it...>
> Subject: Re: [SL] Apache error running summary reports - reality
> 	checking	script?
> To: sql...@li...
> Message-ID: <6FC...@it...>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Just thought I'd post the final resolution to this.
>    Hadn't gotten it over to a VM yet but needed the reports working
> asap so I first updated to the latest and greatest SL, which didn't
> fix it, so then I just did a "yum update", did the postgresql 8
> upgrade shuffle and hey presto!  Reports run instantly like they used
> to!
>
>
> Thanks to all!!!!!!!!
>
> Michael
>
>
> On Jul 21, 2008, at 10:42 AM, Michael Hasse wrote:
>
>> All valid points except that "top" shows CPU/RAM to be just fine
>> while the report is running, as is disk/swap.
>>    This is an older machine, our last non-virtual system, actually,
>> so maybe we'll just go ahead and do the VM migration and see what
>> happens.
>>
>>
>> Thanks,
>>
>> Michael
>>
>> On Jul 21, 2008, at 8:59 AM, Paul Tammes wrote:
>>
>>> Seeing FC4 where 9 is out, postgresql 7.4 where 8.x is out, could
>>> it be the
>>> hardware is old as well?
>>> I know, if it ain't broke and all that ;-)
>>>
>>> If the hardware is not up to speed for a larger number of months,
>>> memory
>>> overflow combined with swapping to (slow/old/olmost dead?) Harddisk
>>> comes to
>>> mind. The change in response between say an AMD Duron 800 and AMD
>>> 4450e
>>> dualcore is stunning.
>>> Both el cheapo cpu but frome different era's alltogether: in
>>> hardware 8
>>> years is a lifetime and a halve.
>>> Nice part: the power consumption of some modern cpu's like 4450e
>>> ore dulcore
>>> intels is stunningly lower.
>>> So that kind of investment earns itself in a few years time as well.
>>>
>>> (If that is too much of an investment, try adding some extra memory
>>> to the
>>> old box.
>>> SD-ram is still available in some antique shops, or second hand on
>>> computer
>>> user club trade fairs.
>>> DDR (sec) is more readilly available, and other than SD-ram (which
>>> is rare,
>>> therefore expensive) pretty cheap as well
>>>
>>> Hth
>>>
>>> 2008/7/21 Michael Hasse <mh...@it...>:
>>>
>>>> Further testing shows that it is indeed something timing out.  The
>>>> reason the test company report ran okay was because there were
>>>> hardly
>>>> any records.  I am also able to run the problem reports okay
>>>> provided
>>>> I choose only a month or two range.  Having run the reports for
>>>> successive months of the entire year with no problems we can at
>>>> least
>>>> get the taxes taken care of, (whew! :), and short of some bizarre
>>>> boundary error this should prove that the data is okay.
>>>>
>>>>   But the question remains of what exactly it is that is timing
>>>> out...?
>>>>
>>>>   In the process of testing this it looks like we actually get any
>>>> of a variety of errors, some of them pretty generic, e.g. plain old
>>>> Apache "Internal server error".
>>>>   (William's suggestions earlier unfortunately did not pan out.)
>>>>
>>>>   This is an FC4 box running:
>>>>       Apache 2.0.54 w/mod_perl 2.0.1
>>>>       Postgresql 7.4.13
>>>>       Perl 5.8.6
>>>>
>>>> Any ideas?
>>>>
>>>>
>>>> Thanks!
>>>>
>>>> Michael
>>>>
>>>>
>>>> ================================
>>>> Based on the advice to check dates I've just been through every  
>>>> date
>>>> value of every record of every table, and I found a couple of bogus
>>>> dates, (you'd think bounds checking would catch '08-27-0200'), and
>>>> fixed them, but still no go.
>>>>    I also checked to see if maybe the version upgrade had missed a
>>>> file due to permissions or something but all the .pl files are the
>>>> same date and perms, (except setup.pl is a few days newer but  
>>>> that's
>>>> to be expected and shouldn't matter).
>>>>    What other things should we be checking?
>>>>    Mismatches between invoices and line items, (e.g. line items
>>>> without invoices)?
>>>>
>>>> <rant>
>>>>    I'm really surprised there are no scripts already written for
>>>> this.  I actually was a rocket scientist, ahem, database  
>>>> programmer,
>>>> in a past life and every project I ever worked on had an "admin
>>>> toolkit" by the end of it with various queries to be sure nothing
>>>> bizarre had slipped through the cracks.  This wasn't intentional,
>>>> but
>>>> all db programmers end up doing some "pre-QA" of their own and the
>>>> scripts just grow naturally from that.
>>>> </rant>
>>>>
>>>>    Anyway, again, suggestions would be greatly appreciated from
>>>> anyone who has dealt with anything like this before...?
>>>>
>>>>
>>>> Thanks!!!!
>>>>
>>>> Michael
>>>>
>>>>
>>>>
>>>> On Jul 3, 2008, at 4:06 AM, ja...@in... wrote:
>>>>
>>>>> A simple sanity check that I wish I had time to implement is to
>>>>> regularly (cron job) :
>>>>> Check each company in the database and hunt for any transactions
>>>>> with illogical (ie stupid) dates
>>>>> such as 07/03/2080 (transposed year digits)
>>>>> Send informative email to user who entered the offending
>>>>> transaction, and copy to sysadmin.
>>>>> Still hoping Dieter might implement something sensible in company
>>>>> defaults to solve this simple problem.
>>>>> Been mentioned before.
>>>>> Very interested in any other sanity checks.
>>>>> DJ
>>>>> On Thu 03/07/08  3:21 PM , Michael Hasse mh...@it... sent:
>>>>> Months later, I'm getting back to this, (prodded by tax
>>>>> deadlines of
>>>>>
>>>>> course!  :)
>>>>>     I did check the timeout directive and raised it to some
>>>>> ridiculous level to no avail, (and same duration of wait so I
>>>>> don't
>>>>>
>>>>> think that's it).
>>>>>     Also don't think it's a record count issue as it was working
>>>>> fine
>>>>> right up a month or two before the upgrade and we don't do THAT
>>>>> much
>>>>>
>>>>> business.
>>>>>     I also opened a terminal session to the host server and
>>>>> watched
>>>>>
>>>>> the stats as it was running and there were no issues with
>>>>> memory/swap/
>>>>> etc running out or anything like that.
>>>>>     Somebody suggested checking another company in the system,
>>>>> (good
>>>>>
>>>>> idea, my apologies for not doing that before posting!  Brain
>>>>> fade...).
>>>>>     Unfortunately that company works just fine so I have to assume
>>>>> at
>>>>> this point that I have a corrupt record somewhere/somehow.
>>>>>     So now the question is - are there any sort of scripts that
>>>>> can
>>>>>
>>>>> be run to do a sanity check?  Has anybody had to deal with bad
>>>>> records and might have some tips to save a few hours of poring
>>>>> over
>>>>>
>>>>> the DB structure?
>>>>> Thanks!!!!!!!!!!!!
>>>>> Michael
>>>>> On Jan 8, 2008, at 6:01 AM, William McKee wrote:
>>>>>> On Mon, Jan 07, 2008 at 09:34:39PM -0800, Michael Hasse wrote:
>>>>>>> Just an update on this.  Permissions are all fine and the  
>>>>>>> reports
>>>>> run
>>>>>>> with no problems in our test company.  Reading up a bit on the
>>>>> errors
>>>>>>> it looks like a simple timeout problem where Apache is giving up
>>>>> on
>>>>>>> the script before it finishes due to the amount of data we have
>>>>>>> slowing the script down.  (System resources are okay so we're  
>>>>>>> not
>>>>>
>>>>>>> running out of memory or anything).
>>>>>>
>>>>>> Interesting, I hadn't considered timeout error causing that
>>>>> message.
>>>>>>
>>>>>>
>>>>>>>    Suggestions/advice are welcome and we'll keep plugging away
>>>>> at it
>>>>>>> and post back if we figure it out.
>>>>>>
>>>>>> Have you checked out the TimeOut directive[1]? I've seen some
>>>>> people
>>>>>> comment the TimeOut does not affect CGI scripts, but Apache
>>>>> security
>>>>>> tips[2] say the following:
>>>>>>
>>>>>> "As TimeOut is currently used for several different operations,
>>>>>
>>>>>> setting
>>>>>> it to a low value introduces problems with long running CGI
>>>>> scripts."
>>>>>>
>>>>>> I've seen others suggest using FastCGI. Keep us posted on your
>>>>>> progress.
>>>>>>
>>>>>>
>>>>>> Good luck,
>>>>>> William
>>>>>>
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> --
>>>>> ---
>>>>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>>>>> Studies have shown that voting for your favorite open source
>>>>> project,
>>>>> along with a healthy diet, reduces your potential for chronic
>>>>> lameness
>>>>> and boredom. Vote Now at http://www.sourceforge.net/community/ 
>>>>> cca08
>>>>> _______________________________________________
>>>>> sql-ledger-users mailing list
>>>>> sql...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> ---
>>>> -
>>>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
>>>> Studies have shown that voting for your favorite open source
>>>> project,
>>>> along with a healthy diet, reduces your potential for chronic
>>>> lameness
>>>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> ----
>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>> challenge
>>>> Build the coolest Linux based applications with Moblin SDK & win
>>>> great
>>>> prizes
>>>> Grand prize is a trip for two to an Open Source event anywhere in
>>>> the world
>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> -
>>> ---
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win
>>> great prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in
>>> the world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 23 Jul 2008 14:06:38 +1000
> From: david <da...@ke...>
> Subject: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID: <1216785998.21483.26.camel@localhost.localdomain>
> Content-Type: text/plain
>
> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to
> 2.8.16 / postgresql 8.3
>
> Are there any migration issues during the transition? In other words,
> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or  
> do I
> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>
> thanks
>
>
> David.
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Tue, 22 Jul 2008 22:09:16 -0700
> From: Michael Hasse <mh...@it...>
> Subject: Re: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID: <B40...@it...>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Don't remember the exact revs but we jumped from 2.6.x to 2.8.x some
> months ago with no problems other than the reporting issue which I've
> covered exhaustively in another thread and that turned out to be
> because we were still on postgresql 7.x so I wouldn't expect that to
> be an issue for you.
>
>
> Thanks,
>
> Michael
>
>
> On Jul 22, 2008, at 9:06 PM, david wrote:
>
>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to
>> 2.8.16 / postgresql 8.3
>>
>> Are there any migration issues during the transition? In other words,
>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or
>> do I
>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>
>> thanks
>>
>>
>> David.
>>
>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 8
> Date: Tue, 22 Jul 2008 23:56:41 -0700 (PDT)
> From: la...@cl...
> Subject: Re: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID:
> 	<447...@ww...>
> Content-Type: text/plain;charset=iso-8859-1
>
> Hello David:
>
> Back in May we had upgraded our production system from
> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at
> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and  
> it's been
> couple months now (with two proven monthends). The main thing was  
> please
> make sure to use the newer 8.3 tools to do the dump, and to use the  
> same
> database encoding for the upgrade.
>
> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it  
> was just
> a simply binary upgrade without the need to touch the data. We also  
> had
> rolled out slony replication on the production cluster and production
> issues had yet to creep up, but we also had only replicated tables  
> that
> were relevant to the IC module.
>
> You should be alright with the 8.1 -> 8.3 upgrade.
>
> Regards,
>
> Tim
>
>
>
>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to
>> 2.8.16 / postgresql 8.3
>>
>> Are there any migration issues during the transition? In other words,
>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or  
>> do I
>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>
>> thanks
>>
>>
>> David.
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 23 Jul 2008 19:04:54 +0200
> From: "Paul Tammes" <pt...@wa...>
> Subject: Re: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID:
> 	<eac...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I remember seeing something in the release notes regarding 'fix  
> behaviour in
> postgresql 8.3.
> So I suggest to first upgrade Ledger, then upgrade postgres. No need  
> to
> invite known bugs to the party, right?
>
> 2008/7/23 <la...@cl...>:
>
>> Hello David:
>>
>> Back in May we had upgraded our production system from
>> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at
>> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and  
>> it's been
>> couple months now (with two proven monthends). The main thing was  
>> please
>> make sure to use the newer 8.3 tools to do the dump, and to use the  
>> same
>> database encoding for the upgrade.
>>
>> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it  
>> was just
>> a simply binary upgrade without the need to touch the data. We also  
>> had
>> rolled out slony replication on the production cluster and production
>> issues had yet to creep up, but we also had only replicated tables  
>> that
>> were relevant to the IC module.
>>
>> You should be alright with the 8.1 -> 8.3 upgrade.
>>
>> Regards,
>>
>> Tim
>>
>>
>>
>>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1 to
>>> 2.8.16 / postgresql 8.3
>>>
>>> Are there any migration issues during the transition? In other  
>>> words,
>>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3? Or  
>>> do I
>>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>>
>>> thanks
>>>
>>>
>>> David.
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win  
>>> great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in  
>>> the
>>> world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>>
>
>
> ------------------------------
>
> Message: 10
> Date: Wed, 23 Jul 2008 10:19:15 -0700
> From: Michael Hasse <mh...@it...>
> Subject: Re: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID: <8DF...@it...>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> And backups!  Lots of backups - at every step!  :)
>
>
> Thanks,
>
> Michael
>
>
> On Jul 23, 2008, at 10:04 AM, Paul Tammes wrote:
>
>> I remember seeing something in the release notes regarding 'fix
>> behaviour in
>> postgresql 8.3.
>> So I suggest to first upgrade Ledger, then upgrade postgres. No
>> need to
>> invite known bugs to the party, right?
>>
>> 2008/7/23 <la...@cl...>:
>>
>>> Hello David:
>>>
>>> Back in May we had upgraded our production system from
>>> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at
>>> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and
>>> it's been
>>> couple months now (with two proven monthends). The main thing was
>>> please
>>> make sure to use the newer 8.3 tools to do the dump, and to use
>>> the same
>>> database encoding for the upgrade.
>>>
>>> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it
>>> was just
>>> a simply binary upgrade without the need to touch the data. We
>>> also had
>>> rolled out slony replication on the production cluster and  
>>> production
>>> issues had yet to creep up, but we also had only replicated tables
>>> that
>>> were relevant to the IC module.
>>>
>>> You should be alright with the 8.1 -> 8.3 upgrade.
>>>
>>> Regards,
>>>
>>> Tim
>>>
>>>
>>>
>>>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1  
>>>> to
>>>> 2.8.16 / postgresql 8.3
>>>>
>>>> Are there any migration issues during the transition? In other
>>>> words,
>>>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3?
>>>> Or do I
>>>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>>>
>>>> thanks
>>>>
>>>>
>>>> David.
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -----
>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>> challenge
>>>> Build the coolest Linux based applications with Moblin SDK & win
>>>> great
>>>> prizes
>>>> Grand prize is a trip for two to an Open Source event anywhere in
>>>> the
>>>> world
>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> ----
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win
>>> great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in
>>> the world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 11
> Date: Wed, 23 Jul 2008 13:42:03 -0700 (PDT)
> From: la...@cl...
> Subject: Re: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID:
> 	<202...@ww...>
> Content-Type: text/plain;charset=iso-8859-1
>
> good point...it definitely was not a single straight shot upgrade.  
> like my
> one year old it was a crawl, walk, and run approach and we were  
> ready to
> "crawl" again if the "walk" had failed. I think SL was upgraded before
> Postgres, and we had to go to 8.x because we needed to implement  
> Slony.
> Plus, based on our upgarde history it will probably be another 3+  
> years
> before there will be another upgarde again...I hope not...Tim
>
>> I remember seeing something in the release notes regarding 'fix  
>> behaviour
>> in
>> postgresql 8.3.
>> So I suggest to first upgrade Ledger, then upgrade postgres. No  
>> need to
>> invite known bugs to the party, right?
>>
>> 2008/7/23 <la...@cl...>:
>>
>>> Hello David:
>>>
>>> Back in May we had upgraded our production system from
>>> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at
>>> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and  
>>> it's
>>> been
>>> couple months now (with two proven monthends). The main thing was  
>>> please
>>> make sure to use the newer 8.3 tools to do the dump, and to use  
>>> the same
>>> database encoding for the upgrade.
>>>
>>> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it  
>>> was
>>> just
>>> a simply binary upgrade without the need to touch the data. We  
>>> also had
>>> rolled out slony replication on the production cluster and  
>>> production
>>> issues had yet to creep up, but we also had only replicated tables  
>>> that
>>> were relevant to the IC module.
>>>
>>> You should be alright with the 8.1 -> 8.3 upgrade.
>>>
>>> Regards,
>>>
>>> Tim
>>>
>>>
>>>
>>>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql 8.1  
>>>> to
>>>> 2.8.16 / postgresql 8.3
>>>>
>>>> Are there any migration issues during the transition? In other  
>>>> words,
>>>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3?  
>>>> Or do
>>> I
>>>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>>>
>>>> thanks
>>>>
>>>>
>>>> David.
>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>> challenge
>>>> Build the coolest Linux based applications with Moblin SDK & win  
>>>> great
>>>> prizes
>>>> Grand prize is a trip for two to an Open Source event anywhere in  
>>>> the
>>>> world
>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win  
>>> great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in  
>>> the
>>> world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>
>
>
>
>
> ------------------------------
>
> Message: 12
> Date: Wed, 23 Jul 2008 15:10:11 -0700
> From: Michael Hasse <mh...@it...>
> Subject: Re: [SL] postgresql 8.3
> To: sql...@li...
> Message-ID: <4B9...@it...>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> IT industry life cycle is 6mo-1yr, business technology life cycle is
> 3-5yrs.
>    This is half of what keeps IT consultants in business, somebody
> has to be around to bridge the gap!   :)
>
>
> Thanks,
>
> Michael
>
>
> On Jul 23, 2008, at 1:42 PM, la...@cl... wrote:
>
>> good point...it definitely was not a single straight shot upgrade.
>> like my
>> one year old it was a crawl, walk, and run approach and we were
>> ready to
>> "crawl" again if the "walk" had failed. I think SL was upgraded  
>> before
>> Postgres, and we had to go to 8.x because we needed to implement
>> Slony.
>> Plus, based on our upgarde history it will probably be another 3+
>> years
>> before there will be another upgarde again...I hope not...Tim
>>
>>> I remember seeing something in the release notes regarding 'fix
>>> behaviour
>>> in
>>> postgresql 8.3.
>>> So I suggest to first upgrade Ledger, then upgrade postgres. No
>>> need to
>>> invite known bugs to the party, right?
>>>
>>> 2008/7/23 <la...@cl...>:
>>>
>>>> Hello David:
>>>>
>>>> Back in May we had upgraded our production system from
>>>> RH7.3/Postgresql7.x/SL2.4 to Centos5.2/Postgresql8.3.1(now at
>>>> 8.3.3)/SL2.8.14(now at 2.8.16). Everything worked out nicely and
>>>> it's
>>>> been
>>>> couple months now (with two proven monthends). The main thing was
>>>> please
>>>> make sure to use the newer 8.3 tools to do the dump, and to use
>>>> the same
>>>> database encoding for the upgrade.
>>>>
>>>> Some extra info. when we upgraded Postgres from 8.3.1 to 8.3.3 it
>>>> was
>>>> just
>>>> a simply binary upgrade without the need to touch the data. We
>>>> also had
>>>> rolled out slony replication on the production cluster and
>>>> production
>>>> issues had yet to creep up, but we also had only replicated
>>>> tables that
>>>> were relevant to the IC module.
>>>>
>>>> You should be alright with the 8.1 -> 8.3 upgrade.
>>>>
>>>> Regards,
>>>>
>>>> Tim
>>>>
>>>>
>>>>
>>>>> I'm thinking of migrating sql-ledger from 2.6.27 / postgresql
>>>>> 8.1 to
>>>>> 2.8.16 / postgresql 8.3
>>>>>
>>>>> Are there any migration issues during the transition? In other
>>>>> words,
>>>>> will the pg-dump from SL 2.6.27 / pg 8.1 talk nicely to pg 8.3?
>>>>> Or do
>>>> I
>>>>> have to upgrade via pg 8.1, and the go to pg 8.3 at the last step?
>>>>>
>>>>> thanks
>>>>>
>>>>>
>>>>> David.
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> ------
>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>>> challenge
>>>>> Build the coolest Linux based applications with Moblin SDK & win
>>>>> great
>>>>> prizes
>>>>> Grand prize is a trip for two to an Open Source event anywhere
>>>>> in the
>>>>> world
>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>>> _______________________________________________
>>>>> sql-ledger-users mailing list
>>>>> sql...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>>
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> -----
>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>> challenge
>>>> Build the coolest Linux based applications with Moblin SDK & win
>>>> great
>>>> prizes
>>>> Grand prize is a trip for two to an Open Source event anywhere in
>>>> the
>>>> world
>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>> _______________________________________________
>>>> sql-ledger-users mailing list
>>>> sql...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> ----
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win
>>> great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in  
>>> the
>>> world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>
>>
>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 13
> Date: Sun, 27 Jul 2008 15:33:38 +0800
> From: Colin Manning <co...@it...>
> Subject: Re: [SL] Sales Invoice Question
> To: sql...@li...
> Message-ID: <488...@it...>
> Content-Type: text/plain; charset="us-ascii"
>
> For your point 1):
>
> You only need to clear the Number - the rest should clear when you  
> update.
>
> Colin.
>
> Munroe Sollog wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> While creating sales invoices, I have 2 re-occurring use issues.  1)
>> Is there a way to easily remove line that was added in error.  At the
>> moment I have to blank out the Description, Number and Item then hit
>> update.  2) Is there a "quick look-up" feature to give me the ability
>> to, without leaving the invoice screen, find an item number to add it
>> to the invoice?
>>
>> Munroe Sollog
>> Systems Engineer
>> Digirati Consulting, Inc
>> so...@di...
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iD8DBQFHzX4BVI0+KepVD/kRAk7WAJ9xeQXzGTsoQmJEqsljV/FEVOaCZACfekwN
>> K4cu1LQdfFbN1CVyZDfpkgI=
>> =SFJE
>> -----END PGP SIGNATURE-----
>>
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>
>
>
> ------------------------------
>
> Message: 14
> Date: Tue, 29 Jul 2008 16:33:02 -0700
> From: Michael Hasse <mh...@it...>
> Subject: Re: [SL] Sales Invoice Question
> To: sql...@li...
> Message-ID: <2DD...@it...>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> This does appear to be fairly new functionality.  Recent versions
> have still required that pretty much the whol line item be blanked
> out.  Good to see this works now!
>    Regarding point #2, one can just do a New Window.  Or if that
> ties up too much screen real-estate, simply type a portion of the
> part number or description, (not both!), and when you hit Update it
> will show you a list of possible matches.
>
>
> Thanks,
>
> Michael Hasse
> Itwerx
> 206-850-1496
> http://www.itwerx.net/
>
> **********************************
> If our service is not 100% satisfactory please tell us!
> If it is 100% please tell others!
> **********************************
>
> On Jul 27, 2008, at 12:33 AM, Colin Manning wrote:
>
>> For your point 1):
>>
>> You only need to clear the Number - the rest should clear when you
>> update.
>>
>> Colin.
>>
>> Munroe Sollog wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> While creating sales invoices, I have 2 re-occurring use issues.  1)
>>> Is there a way to easily remove line that was added in error.  At  
>>> the
>>> moment I have to blank out the Description, Number and Item then hit
>>> update.  2) Is there a "quick look-up" feature to give me the  
>>> ability
>>> to, without leaving the invoice screen, find an item number to add  
>>> it
>>> to the invoice?
>>>
>>> Munroe Sollog
>>> Systems Engineer
>>> Digirati Consulting, Inc
>>> so...@di...
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.6 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>>
>>> iD8DBQFHzX4BVI0+KepVD/kRAk7WAJ9xeQXzGTsoQmJEqsljV/FEVOaCZACfekwN
>>> K4cu1LQdfFbN1CVyZDfpkgI=
>>> =SFJE
>>> -----END PGP SIGNATURE-----
>>>
>>>
>>> ---------------------------------------------------------------------
>>> ----
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> sql-ledger-users mailing list
>>> sql...@li...
>>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>>
>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>
>
>
>
> ------------------------------
>
> Message: 15
> Date: Sun, 03 Aug 2008 21:39:41 -0400
> From: Munroe Sollog <so...@di...>
> Subject: [SL] Error after moving sql-ledger to a new server
> To: sql...@li...
> Message-ID: <489...@di...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> We just moved sql-ledger to a new physical server and most thing work,
> however I went to post a payment and now I get:
>
> *DBD::Pg::db do failed: ERROR: syntax error at or near ")"*
> *LINE 4: '07-11-08', NULL, )*
> * ^ at SL/IS.pm line 1077.*
>
> Error!
> *INSERT INTO acc_trans (trans_id, chart_id, amount,*
> * transdate, project_id, id)*
> * VALUES (10498, 10032, 3522,*
> * '07-11-08', NULL, )*
> *ERROR: syntax error at or near ")"*
> *LINE 4: '07-11-08', NULL, )*
> * ^*
>
> -- 
> Munroe Sollog
> Systems Engineer
> Digirati Consulting, Inc
> so...@di...
>
>
>
>
>
> ------------------------------
>
> Message: 16
> Date: Mon, 11 Aug 2008 07:51:47 -0400
> From: Munroe Sollog <so...@di...>
> Subject: [SL] problem emailing invoices
> To: sql...@li...
> Message-ID: <48A...@di...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I am getting this error whenever I try to email an invoice:
>
> panic: attempt to copy freed scalar 83e62c8 to 8234d50 at SL/Form.pm
> line 984.
>
> I have just upgraded to 2.8.18 in an attempt to fix the problem, but
> no go.  This is a debian system.
>
> -- 
> Munroe Sollog
> Systems Engineer
> Digirati Consulting, Inc
> so...@di...
>
>
>
>
> ------------------------------
>
> Message: 17
> Date: Mon, 11 Aug 2008 18:00:44 +0200
> From: "Paul Tammes" <pt...@wa...>
> Subject: Re: [SL] problem emailing invoices
> To: sql...@li...
> Message-ID:
> 	<eac...@ma...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I do not know what a freed scalar is, maybe a missing font?
>
> 2008/8/11 Munroe Sollog <so...@di...>
>
>> I am getting this error whenever I try to email an invoice:
>>
>> panic: attempt to copy freed scalar 83e62c8 to 8234d50 at SL/Form.pm
>> line 984.
>>
>> I have just upgraded to 2.8.18 in an attempt to fix the problem, but
>> no go.  This is a debian system.
>>
>> --
>> Munroe Sollog
>> Systems Engineer
>> Digirati Consulting, Inc
>> so...@di...
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>>
>
>
> ------------------------------
>
> Message: 18
> Date: Mon, 11 Aug 2008 09:06:31 -0700
> From: Bob Miller <bo...@co...>
> Subject: Re: [SL] problem emailing invoices
> To: sql...@li...
> Message-ID: <1218470791.20661.1155.camel@spot>
> Content-Type: text/plain
>
> Check here:
> http://abacus.sql-ledger.com/userforum/forum_entry.php?id=1046&PHPSESSID=fedb49929e4faf8209d6b3fe1a8e08ef
>
> -----Original Message-----
> From: Munroe Sollog <so...@di...>
> Reply-To: sql...@li...
> To: sql...@li...
> Subject: [SL] problem emailing invoices
> Date: Mon, 11 Aug 2008 07:51:47 -0400
>
>
> I am getting this error whenever I try to email an invoice:
>
> panic: attempt to copy freed scalar 83e62c8 to 8234d50 at SL/Form.pm
> line 984.
>
> I have just upgraded to 2.8.18 in an attempt to fix the problem, but
> no go.  This is a debian system.
>
>
> Bob Miller
> 334-7117/633-3760
> http://computerisms.ca
> bo...@co...
> Network, Internet, Server,
> and Open Source Solutions
>
>
> ------------------------------
>
> Message: 19
> Date: Mon, 11 Aug 2008 12:33:05 -0400
> From: Munroe Sollog <so...@di...>
> Subject: Re: [SL] problem emailing invoices
> To: sql...@li...
> Message-ID: <48A...@di...>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Bob -
>
> yea, I found that forum post a little while after I sent this  
> email.  I
> even posted into that thread as it seemed the place this problem was
> being discussed.  I am in the process now of building another  
> machine to
> put etch on so I can get sql-ledger working again.  But I would like a
> better solution as this box is not production material.
>
> Munroe Sollog
> Systems Engineer
> Digirati Consulting, Inc
> so...@di...
>
>
>
>
> Bob Miller wrote:
>> Check here:
>> http://abacus.sql-ledger.com/userforum/forum_entry.php?id=1046&PHPSESSID=fedb49929e4faf8209d6b3fe1a8e08ef
>>
>> -----Original Message-----
>> From: Munroe Sollog <so...@di...>
>> Reply-To: sql...@li...
>> To: sql...@li...
>> Subject: [SL] problem emailing invoices
>> Date: Mon, 11 Aug 2008 07:51:47 -0400
>>
>>
>> I am getting this error whenever I try to email an invoice:
>>
>> panic: attempt to copy freed scalar 83e62c8 to 8234d50 at SL/Form.pm
>> line 984.
>>
>> I have just upgraded to 2.8.18 in an attempt to fix the problem, but
>> no go.  This is a debian system.
>>
>>
>> Bob Miller
>> 334-7117/633-3760
>> http://computerisms.ca
>> bo...@co...
>> Network, Internet, Server,
>> and Open Source Solutions
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> sql-ledger-users mailing list
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>>
>
>
>
> ------------------------------
>
> Message: 20
> Date: Mon, 11 Aug 2008 09:49:27 -0700
> From: Bob Miller <bo...@co...>
> Subject: Re: [SL] problem emailing invoices
> To: sql...@li...
> Message-ID: <1218473367.20661.1172.camel@spot>
> Content-Type: text/plain
>
> Munroe:
> Good luck.  I spent a week looking for solutions to this problem, a  
> week
> I am still catching up from.  sometimes the best solution isn't the  
> most
> elegant one....
> The guys over at ledgersmb are aware of the issue and are working on  
> it,
> as far as I know, so might be worth keeping an eye on what they find
> over there.
>
>
> -----Original Message-----
> From: Munroe Sollog <so...@di...>
> Reply-To: sql...@li...
> To: sql...@li...
> Subject: Re: [SL] problem emailing invoices
> Date: Mon, 11 Aug 2008 12:33:05 -0400
>
>
> Bob -
>
> yea, I found that forum post a little while after I sent this  
> email.  I
> even posted into that thread as it seemed the place this problem was
> being discussed.  I am in the process now of building another  
> machine to
> put etch on so I can get sql-ledger working again.  But I would like a
> better solution as this box is not production material.
>
> Munroe Sollog
> Systems Engineer
> Digirati Consulting, Inc
> so...@di...
>
>
>
>
> Bob Miller wrote:
>> Check here:
>> http://abacus.sql-ledger.com/userforum/forum_entry.php?id=1046&PHPSESSID=fedb49929e4faf8209d6b3fe1a8e08ef
>>
>> -----Original Message-----
>> From: Munroe Sollog <so...@di...>
>> Reply-To: sql...@li...
>> To: sql...@li...
>> Subject: [SL] problem emailing invoices
>> Date: Mon, 11 Aug 2008 07:51:47 -0400
>>
>>
>> I am getting this error whenever I try to email an invoice:
>>
>> panic: attempt to copy freed scalar 83e62c8 to 8234d50 at SL/Form.pm
>> line 984.
>>
>> I have just upgraded to 2.8.18 in an attempt to fix the problem, but
>> no go.  This is a debian system.
>>
>>
>> Bob Miller
>> 334-7117/633-3760
>> http://computerisms.ca
>> bo...@co...
>> Network, Internet, Server,
>> and Open Source Solutions
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great prizes
>> Grand prize is a trip for two to an Open Source e...
 
[truncated message content]

[Off Topic] unsubscribe

[Didier D. <Did...@li...>]

Hi=09

How can I unsubscribe withour my password?

Thanks,
Didier