sql-ledger-users — SQL-Ledger users

Re: [SL] upgrade issues...

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

 > It's mailing list threads like this that make me start to question...
----------------------------------
At first blush I would agree, but this isn't really normal for  
Dieter.  He may be a bit brief at times but Dieter usually comes  
across as a regular guy running a small business and treating his  
paying customers right.  These few posts sound more like the  
stereotypical programmer-curmudgeon growling at the rest of humanity.
    However, this is the flip side of the great advantage of only  
having to deal with one person, you only have one person to deal  
with!  If they are stressed out in some other part of their life one  
gets the spillover without any context.
    So let's give Dieter the benefit of the doubt and wish him the best.


Thanks,

Michael


On Feb 6, 2008, at 10:11 AM, Roy W Pennington wrote:

> On February 6, 2008, Dieter Simader wrote:
>> On Wed, 6 Feb 2008, Roy W Pennington wrote:
>>
>>> On February 5, 2008, Dieter Simader wrote:
>>>> duh, Roy, if this error does not happen in the upgrade from  
>>>> 2.6.27-2.8.0
>>>> but it happens in the upgrade 2.8.0-2.8.2 why should it be in  
>>>> the UPGRADE
>>>> docs for 2.6.27-2.8.0 ?
>>>>
>>> But it DOES happen when upgrading from 2.6.27 to 2.8.12
>>
>> Roy, I told you the error happens when you upgrade from 2.8.0-2.8.2
>
> Yes i realized that weh i read the 1st replys  to this thread... as  
> you so eloquently say....DUH.
> but.. from a user stand point you are upgrading in 1 functional  
> step, regardless of what the scripts are doing behind the scene.
>
>> The fact that you are upgrading from 2.6.27 has nothing to do with  
>> the
>> error when it happens. If you were to upgrade to 2.8.0 there is no  
>> such
>> error but because you are continuing with the upgrade to 2.8.12  
>> the error
>> crops up. Do you understand it now?
>
> Yes i understand it.
> My point was it is not intuitive.
>> From a user stand point you are upgrading in 1 functional step,  
>> regardless of what the scripts are doing behind the scene.
> The fantastic upgrade method simplifies the process to 1 simple  
> step, but the docs are set up to assume that the user realizes that  
> the script does it in multiple steps.
> It is not intuitive to read multiple upgrade documents  
> (2.6.27-2.8.0 then 2.8.0-2.8.x etc etc) when from a user standpoint  
> you are seemingly upgrading in 1 step.
>
>>> I never meant to suggest it should be in the 2.6.27-2.8.0 doc
>>
>> Yes, this is what you suggested and are still suggesting, see above.
>
> NO. If you read my last post.... you may see that i am suggesting  
> that there MAY be ANOTHER way to document the process.
> It could be simply creating another doc called '2.6.27-2.8.12  
> upgrade'  or adding it to the faq or in the readme file or whatever...
> My point is the docs are not totally inuitive, and that can lead to  
> otherwise needless questions.
>
>
> Do with that input as you wish.
>
> Roy
>
> FWIW, as a successful, former business owner who will be retiring  
> early to go travel the world on his sailboat....
> I learned long ago, that replying to customers in a seemingly  
> condescending way does little to help improve revenue.
> During the current transition to the new owners, I have suggested  
> that they use SQL-ledger and pay for ongoing support. It's mailing  
> list threads like this that make me start to question my advice to  
> them.
>
> ---------------------------------------------------------------------- 
> ---
> 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

Re: [SL] upgrade issues...

[Roy W P. <arc...@mt...>]

On February 6, 2008, Dieter Simader wrote:
> On Wed, 6 Feb 2008, Roy W Pennington wrote:
> 
> > On February 5, 2008, Dieter Simader wrote:
> >> duh, Roy, if this error does not happen in the upgrade from 2.6.27-2.8.0
> >> but it happens in the upgrade 2.8.0-2.8.2 why should it be in the UPGRADE
> >> docs for 2.6.27-2.8.0 ?
> >>
> > But it DOES happen when upgrading from 2.6.27 to 2.8.12
> 
> Roy, I told you the error happens when you upgrade from 2.8.0-2.8.2

Yes i realized that weh i read the 1st replys  to this thread... as you so eloquently say....DUH.
but.. from a user stand point you are upgrading in 1 functional step, regardless of what the scripts are doing behind the scene.
 
> The fact that you are upgrading from 2.6.27 has nothing to do with the 
> error when it happens. If you were to upgrade to 2.8.0 there is no such 
> error but because you are continuing with the upgrade to 2.8.12 the error 
> crops up. Do you understand it now?

Yes i understand it. 
My point was it is not intuitive.
From a user stand point you are upgrading in 1 functional step, regardless of what the scripts are doing behind the scene.
The fantastic upgrade method simplifies the process to 1 simple step, but the docs are set up to assume that the user realizes that the script does it in multiple steps.
It is not intuitive to read multiple upgrade documents (2.6.27-2.8.0 then 2.8.0-2.8.x etc etc) when from a user standpoint you are seemingly upgrading in 1 step.
 
> > I never meant to suggest it should be in the 2.6.27-2.8.0 doc
> 
> Yes, this is what you suggested and are still suggesting, see above.

NO. If you read my last post.... you may see that i am suggesting that there MAY be ANOTHER way to document the process. 
It could be simply creating another doc called '2.6.27-2.8.12 upgrade'  or adding it to the faq or in the readme file or whatever...
My point is the docs are not totally inuitive, and that can lead to otherwise needless questions.


Do with that input as you wish. 

Roy

FWIW, as a successful, former business owner who will be retiring early to go travel the world on his sailboat.... 
I learned long ago, that replying to customers in a seemingly condescending way does little to help improve revenue.
During the current transition to the new owners, I have suggested that they use SQL-ledger and pay for ongoing support. It's mailing list threads like this that make me start to question my advice to them.

Re: [SL] upgrade issues...

[Dieter S. <dsi...@sq...>]

On Wed, 6 Feb 2008, Roy W Pennington wrote:

> On February 5, 2008, Dieter Simader wrote:
>> duh, Roy, if this error does not happen in the upgrade from 2.6.27-2.8.0
>> but it happens in the upgrade 2.8.0-2.8.2 why should it be in the UPGRADE
>> docs for 2.6.27-2.8.0 ?
>>
> But it DOES happen when upgrading from 2.6.27 to 2.8.12

Roy, I told you the error happens when you upgrade from 2.8.0-2.8.2

The fact that you are upgrading from 2.6.27 has nothing to do with the 
error when it happens. If you were to upgrade to 2.8.0 there is no such 
error but because you are continuing with the upgrade to 2.8.12 the error 
crops up. Do you understand it now?

> I never meant to suggest it should be in the 2.6.27-2.8.0 doc

Yes, this is what you suggested and are still suggesting, see above.

Re: [SL] upgrade issues...

[Dieter S. <dsi...@sq...>]

On Wed, 6 Feb 2008, Armaghan Saqib wrote:

> On 2/6/08, Dieter Simader <dsi...@sq...> wrote:
>> come on, Armaghan, what a crock.
>
> What I did mean was upgrade through ****sql scripts **** is

And this is different, how?

SQL-Ledger runs the scripts for you, there is no need to run these scripts 
manually.

> incremental. I did not say that you need to install each incremental
> SL version to upgrade.

Yes you did!

>
> I do this almost on daily basis for my hosting customers and just run
> the sql-scripts. Have also documented it on my sql-ledger WIKI at

Business must be really good for you if you are upgrading on a daily 
basis.

> wiki.ledger123.com. See:
>
> http://wiki.ledger123.com/index.php?n=Local.Upgrades and
> http://wiki.ledger123.com/index.php?n=Development.PostgreSQL

You are not doing anyone a favour by distributing false information.

Re: [SL] upgrade issues...

[Roy W P. <arc...@mt...>]

On February 5, 2008, Dieter Simader wrote:
> duh, Roy, if this error does not happen in the upgrade from 2.6.27-2.8.0 
> but it happens in the upgrade 2.8.0-2.8.2 why should it be in the UPGRADE 
> docs for 2.6.27-2.8.0 ?
> 
But it DOES happen when upgrading from 2.6.27 to 2.8.12
I never meant to suggest it should be in the 2.6.27-2.8.0 doc

> BTW, this error was done delibertly so people wouldn't have to mess around 
> with the upgrade scripts. I could have left the oneliner which is in 
> Pg-upgrade-2.8.0-2.8.2.sql in the next upgrade script and have you edit
> the upgrade scripts instead.
> 
> Which is easier, load admin.pl, unlock the system and log in again or have 
> you edit the upgrade script?

obvious answer

FWIW
As you know, I own a copy of the manual and have used SL for a while. I'm familiar with the traditional upgrade process and yet...
I read the 2.6.27-2.8.0 upgrade docs and the readme that the setup script always gives the option to display, and didn't see a mention of the possible error.
I guess i could have read the 2.6.12-2.8.0 upgrade docs AND then  2.8.0-2.8.x upgrade docs, but it's not intuitive to read docs for a 2.8.0-2.8.12 upgrade when you aren't upgrading from 2.8.0...

That said, it would be a pain to keep having to create upgrade docs for every possible upgrade combination.
I'm someone who reads docs and yet I didn't read anything about the error being expected.  
Maybe stick a comment in the readme or FAQ ?  who knows....  

It's not a criticism so don't take it that way.  it's a suggestion in the interest of making things easier for everyone.
IMO, any way to prevent people from littering the list with questions to documented answers is a good thing.

Cheers,
Roy

Re: [SL] Timeout on AR::Reports::Outstanding

[Martin B. <boe...@gm...>]

OK,

I ran the ./ar.pl call from the command line with 'perl -d' and traced the 
execution. It stopped at SL/AA.pl(955) $sth->execute(); when it sends data to 
the database => Problem must be with Postgresql.

Switched on verbosity and debugging on postgres and found that when I send the 
query I get a:

> LOG:  could not send data to client: Operation not permitted

Google doesn't know anything about it, but I am highly sure its because I have 
an IPv6 address in /etc/hosts for localhost AND and IPv4. Changing it to 
127.0.0.1 and the timeout disappears. Instead I get a:

> DBD::Pg::st execute failed: out of memory for query result
> lost synchronization with server: got message type " ", length 1382381157

Also strange: To doublecheck that this is the cause (for whatever reasons, 
btw) I wrote this tiny perl program that just runs the query:

> use DBI;
> my $dbh = DBI->connect( 'dbi:Pg:dbname=ledger_maxnet;host=localhost',
>                         'pgsql',
>                         '',
>   );
>
> my $sth = $dbh->prepare($query);
> $sth->execute;

$query holds the SQL query that fails on the web-application. This ALWAYS 
WORKS, I called it hundred times.. You can skip the ";host=localhost" 
parameter, it makes no differences, it just works.

So it remains mystic. I have a memory error now I don't know how to fix. I 
already changed max_connections, shared_buffers, work_mem etc..  but it 
doesn't solve it. Also I tried to tune kernel parameters like 
kern.ipc.shmmax . The postgresql community suggests to use cursors for large 
results - but after all 256 rows isn't to much for that 1GB ram+1GB swap 
machine that I run it on by far.


Martin




On Tuesday 05 February 2008 11:37:57 Armaghan Saqib wrote:
> Martin Boese wrote:
> > On Monday 04 February 2008 17:16:21 Armaghan Saqib wrote:
> > (...)
> >
> >> Seems really strange error. Is this happening with all reports or just
> >> with these two?
> >>
> >> Sometimes the left joins can take the database down for simple queries
> >> if there is no department/warehouse defined. But your testing does not
> >> point to database.
> >>
> >> Which version of postgres? Try doing vacuumdb to the database
> >
> > I am using 8.2.5 . I actually upgraded from 8.1 just to see if this
> > problem will disappear.
> > I suspect more a DBD/DBI problem... Is there any way to test SL cgi
> > script from the command line?
>
> Put the following in a shell script and run in the sql-ledger folder.
> Make sure that line starting with ./ar.pl till end is one line.
>
> #!/usr/local/bin/bash
>
> ./ar.pl
> "path=bin/mozilla&login=armaghan&password=armaghan&action=continue&nextsub=
>transactions&summarY=1&open=Y&l_amount=Y&l
> _description=Y&l_invnumber=Y&l_name=Y&l_paid=Y&l_transdate=Y&vc=customer&AR
>AP=AR&outstanding=1"
>
> --
> Purpose-built SQL-Ledger Hosting
> http://www.ledger123.com/
>
> Free trial available.

Re: [SL] upgrade issues...

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

On 2/6/08, Dieter Simader <dsi...@sq...> wrote:
> come on, Armaghan, what a crock.

What I did mean was upgrade through ****sql scripts **** is
incremental. I did not say that you need to install each incremental
SL version to upgrade.

I do this almost on daily basis for my hosting customers and just run
the sql-scripts. Have also documented it on my sql-ledger WIKI at
wiki.ledger123.com. See:

http://wiki.ledger123.com/index.php?n=Local.Upgrades and
http://wiki.ledger123.com/index.php?n=Development.PostgreSQL

Sorry for causing any confusion to list members.

Regards

-- 
Purpose-built SQL-Ledger Hosting
http://www.ledger123.com/

Free trial available.
--

Re: [SL] upgrade issues...

[Dieter S. <dsi...@sq...>]

duh, Roy, if this error does not happen in the upgrade from 2.6.27-2.8.0 
but it happens in the upgrade 2.8.0-2.8.2 why should it be in the UPGRADE 
docs for 2.6.27-2.8.0 ?

BTW, this error was done delibertly so people wouldn't have to mess around 
with the upgrade scripts. I could have left the oneliner which is in 
Pg-upgrade-2.8.0-2.8.2.sql in the next upgrade script and have you edit
the upgrade scripts instead.

Which is easier, load admin.pl, unlock the system and log in again or have 
you edit the upgrade script?


On Tue, 5 Feb 2008, Roy W Pennington wrote:

> Thanks Michael & Adam !
>
> the section mentioned in the archive post that Adam linked  to:
>
> -----------------
> 3. If you receive the following error while upgrading
>
> ERROR: trigger "del_recurring" for table "oe" does not exist
>
> load admin.pl and "Unlock" the system.
>
> 4. log in
> ---------------------
>
> isn't in the doc for UPGRADE-2.6.27-2.8.0
> but it is in the docs UPGRADE-2.8.0-2.8.2, UPGRADE-2.8.2-2.8.4  etc
>
> There is no doc named "UPGRADE-2.6.27-2.8.12"....  is that an oversight ?
> or is it recommended to upgrade to 2.8. then incrementally to 2.8.12 ?
>
>

Re: [SL] upgrade issues...

[Dieter S. <dsi...@sq...>]

come on, Armaghan, what a crock.

The upgrade can be done for any version from 1.2.7 onward without an 
incremental upgrade.

This bit of information is even posted on the website at

http://sql-ledger.com/cgi-bin/nav.pl?page=source/index.html&title=Download

<quote>
Upgrading from any version > 1.2.7 to the latest version

Upgrading is easy. Load setup.pl from the sql-ledger root directory and 
select Upgrade. The script will lock everyone out and install the new code 
over top. The only thing left to do is to log in to upgrade a dataset.

To upgrade manually load admin.pl and Lock the system. Download the new 
code and untar over top and fix the permissions according to the UPGRADE 
file in the doc directory. Most of the time there is nothing else to be 
done. Load admin.pl and Unlock the system. When a user logs in the Dataset 
is upgraded automatically, you do not have to do anything. If other steps 
are required, i.e template modifications, they will be listed in the 
UPGRADE file.
You DO NOT have to install intermediate versions to upgrade to the latest 
version! Intermediate upgrades are done for you.
</unquote>


On Wed, 6 Feb 2008, Armaghan Saqib wrote:

> Roy W Pennington wrote:
>> isn't in the doc for UPGRADE-2.6.27-2.8.0
>> but it is in the docs UPGRADE-2.8.0-2.8.2, UPGRADE-2.8.2-2.8.4  etc
>>
>> There is no doc named "UPGRADE-2.6.27-2.8.12"....  is that an oversight ?
>> or is it recommended to upgrade to 2.8. then incrementally to 2.8.12 ?
> Yes, the incremental upgrade is the recommended (and the only) way and
> seems logical because every upgrade script is written whenever a new
> (incremental) release comes out.
>
> Armaghan
>
>

Re: [SL] upgrade issues...

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

Roy W Pennington wrote:
> isn't in the doc for UPGRADE-2.6.27-2.8.0
> but it is in the docs UPGRADE-2.8.0-2.8.2, UPGRADE-2.8.2-2.8.4  etc
>
> There is no doc named "UPGRADE-2.6.27-2.8.12"....  is that an oversight ?
> or is it recommended to upgrade to 2.8. then incrementally to 2.8.12 ? 
Yes, the incremental upgrade is the recommended (and the only) way and 
seems logical because every upgrade script is written whenever a new 
(incremental) release comes out.

Armaghan

-- 
Purpose-built SQL-Ledger Hosting
http://www.ledger123.com/

Free trial available.
-- 

Re: [SL] upgrade issues...

[Roy W P. <arc...@mt...>]

Thanks Michael & Adam !

the section mentioned in the archive post that Adam linked  to:

-----------------
3. If you receive the following error while upgrading

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

load admin.pl and "Unlock" the system.

4. log in
---------------------

isn't in the doc for UPGRADE-2.6.27-2.8.0
but it is in the docs UPGRADE-2.8.0-2.8.2, UPGRADE-2.8.2-2.8.4  etc

There is no doc named "UPGRADE-2.6.27-2.8.12"....  is that an oversight ?
or is it recommended to upgrade to 2.8. then incrementally to 2.8.12 ?  

-- 
Roy Pennington
Arch Distributors of Canada
Phone: 204.257.8161

Re: [SL] upgrade issues...

[Adam V. <amv...@gm...>]

Roy W Pennington wrote:
> Afternoon everyone !
> Long time no talk/email !
>
> I finally got around to upgrading (from 2.6.27  to 2.8.12)
>
> I copied the setup.pl script into the /usr/local/sql-ledger and ran it.
> then i followed the docs for the 2.6. to 2.8 upgrade...  copied the templates... removed the filename prefix....
>
> i logged in and.....
>
> Upgrading to Version 2.8.12 ...
> Error!
>
> drop trigger del_recurring ON oe
> ERROR: trigger "del_recurring" for table "oe" does not exist
>
> I would assume that the upgrade script assumed i was using 2.7 or newer and it complained about a table that doesn't exist in 2.6.27 ?
> The 2.8 manual makes no mention of special way of upgrading from 2.6
>
> I assume other have run into this ?
> What  do i do now ?
>
>   
http://sourceforge.net/mailarchive/message.php?msg_id=20070511152330.M943%40gumby.simtax.ca

-- 
Adam Vandemore
Systems Administrator
IMED Mobility

Re: [SL] upgrade issues...

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

As I recall that error is "normal" and you can just re-login and it  
will be fine.


Thanks,

Michael


On Feb 5, 2008, at 10:57 AM, Roy W Pennington wrote:

> Afternoon everyone !
> Long time no talk/email !
>
> I finally got around to upgrading (from 2.6.27  to 2.8.12)
>
> I copied the setup.pl script into the /usr/local/sql-ledger and ran  
> it.
> then i followed the docs for the 2.6. to 2.8 upgrade...  copied the  
> templates... removed the filename prefix....
>
> i logged in and.....
>
> Upgrading to Version 2.8.12 ...
> Error!
>
> drop trigger del_recurring ON oe
> ERROR: trigger "del_recurring" for table "oe" does not exist
>
> I would assume that the upgrade script assumed i was using 2.7 or  
> newer and it complained about a table that doesn't exist in 2.6.27 ?
> The 2.8 manual makes no mention of special way of upgrading from 2.6
>
> I assume other have run into this ?
> What  do i do now ?
>
> -- 
> Roy Pennington
> Arch Distributors of Canada
> Phone: 204.257.8161
>
> ---------------------------------------------------------------------- 
> ---
> 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

[SL] upgrade issues...

[Roy W P. <arc...@mt...>]

Afternoon everyone !
Long time no talk/email !

I finally got around to upgrading (from 2.6.27  to 2.8.12)

I copied the setup.pl script into the /usr/local/sql-ledger and ran it.
then i followed the docs for the 2.6. to 2.8 upgrade...  copied the templates... removed the filename prefix....

i logged in and.....

Upgrading to Version 2.8.12 ...
Error!

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

I would assume that the upgrade script assumed i was using 2.7 or newer and it complained about a table that doesn't exist in 2.6.27 ?
The 2.8 manual makes no mention of special way of upgrading from 2.6

I assume other have run into this ?
What  do i do now ?

-- 
Roy Pennington
Arch Distributors of Canada
Phone: 204.257.8161

Re: [SL] Timeout on AR::Reports::Outstanding

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

Martin Boese wrote:
> On Monday 04 February 2008 17:16:21 Armaghan Saqib wrote:
> (...)
>   
>> Seems really strange error. Is this happening with all reports or just
>> with these two?
>>
>> Sometimes the left joins can take the database down for simple queries
>> if there is no department/warehouse defined. But your testing does not
>> point to database.
>>
>> Which version of postgres? Try doing vacuumdb to the database
>>     
>
> I am using 8.2.5 . I actually upgraded from 8.1 just to see if this problem 
> will disappear.
> I suspect more a DBD/DBI problem... Is there any way to test SL cgi script 
> from the command line?
>
>   
Put the following in a shell script and run in the sql-ledger folder. 
Make sure that line starting with ./ar.pl till end is one line.

#!/usr/local/bin/bash

./ar.pl 
"path=bin/mozilla&login=armaghan&password=armaghan&action=continue&nextsub=transactions&summarY=1&open=Y&l_amount=Y&l
_description=Y&l_invnumber=Y&l_name=Y&l_paid=Y&l_transdate=Y&vc=customer&ARAP=AR&outstanding=1"

-- 
Purpose-built SQL-Ledger Hosting
http://www.ledger123.com/

Free trial available.
-- 

Re: [SL] Timeout on AR::Reports::Outstanding

[Martin B. <boe...@gm...>]

On Monday 04 February 2008 17:16:21 Armaghan Saqib wrote:
(...)
> Seems really strange error. Is this happening with all reports or just
> with these two?
>
> Sometimes the left joins can take the database down for simple queries
> if there is no department/warehouse defined. But your testing does not
> point to database.
>
> Which version of postgres? Try doing vacuumdb to the database

I am using 8.2.5 . I actually upgraded from 8.1 just to see if this problem 
will disappear.
I suspect more a DBD/DBI problem... Is there any way to test SL cgi script 
from the command line?


Martin

Re: [SL] Timeout on AR::Reports::Outstanding

[Dirk E. S. <ds...@ca...>]

>
> AR::Reports::Outstanding::next should show me all outstanding invoices.
> But
> loading the page times out (it stays busy all time without displaying
> anything on all browsers).

I had something similar, caused buy a stupid little mistake: A user had
registered transactions in the far future, around year 20007. It would
take an eternity to get reports as the javascript loading the date-options
was eating all the browser memory. - Maybe thats your problem; Just call a
trial balance starting next year (2009) until infinity....

Hope it helps

Enrique

-- 
Dirk Enrique Seiffert - Lintec S.A.
Ed. Torre del Reloj - Of. 401
Plaza de los Coches, Centro
Cartagena - Colombia
http://www.lintecsa.com

Re: [SL] Timeout on AR::Reports::Outstanding

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

Martin Boese wrote:
> AR::Reports::Outstanding::next should show me all outstanding invoices. But 
> loading the page times out (it stays busy all time without displaying 
> anything on all browsers).
>
> If I stop the postgresql database server while waiting for the result I get 
> the following error:
>
>   
>> DBD::Pg::st execute failed: server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>> Error!
>>
>> SELECT a.id, a.invnumber, a.ordnumber, a.transdate,
>> a.duedate, (SELECT sum(ac.amount)
>> FROM acc_trans ac
>> JOIN chart c ON (c.id = ac.chart_id)
>> WHERE ac.trans_id = a.id
>> AND ac.approved = '1'
>> AND c.link LIKE '%_tax%') * 1 AS tax,
>> a.amount, (SELECT SUM(ac.amount) * -1 * 1
>> FROM acc_trans ac
>> JOIN chart c ON (c.id = ac.chart_id)
>> WHERE ac.trans_id = a.id
>> AND ac.approved = '1'
>> AND (c.link LIKE '%AR_paid%'
>> OR c.link LIKE '%AR_discount%'
>> OR c.link = '')) AS paid,
>> a.invoice, a.datepaid, a.terms, a.notes,
>> a.shipvia, a.waybill, a.shippingpoint,
>> e.name AS employee, vc.name, vc.customernumber,
>> a.customer_id, a.till, m.name AS manager, a.curr,
>> a.exchangerate, d.description AS department,
>> a.ponumber, a.warehouse_id, w.description AS warehouse,
>> a.description, a.dcn, pm.description AS paymentmethod,
>> a.datepaid - a.duedate AS paymentdiff,
>> ad.address1, ad.address2, ad.city, ad.zipcode, ad.country
>>
>> FROM ar a
>> JOIN customer vc ON (a.customer_id = vc.id)
>> JOIN address ad ON (ad.trans_id = vc.id)
>> LEFT JOIN employee e ON (a.employee_id = e.id)
>> LEFT JOIN employee m ON (e.managerid = m.id)
>> LEFT JOIN department d ON (a.department_id = d.id)
>> LEFT JOIN warehouse w ON (a.warehouse_id = w.id)
>> LEFT JOIN paymentmethod pm ON (pm.id = a.paymentmethod_id)
>>
>>
>> WHERE a.approved = '1'
>> ORDER by 4 ASC,2,17
>> server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>>     
>
>
> So it seems that the server was busy fetching an sql-select. However if I take 
> this query and paste it manually into psql I __instantly__ get the result 
> (256 rows), so I don't think it's a problem of the database. Also my database 
> is very small - about 64kb tar-gzip.
>
> I am using FreeBSD 6.2 with Perl 5.8.8 (base system installations) with:
> p5-DBD-Pg-1.49, p5-DBI-1.60.1, Sql-ledger 2.8.11 (happend also in earlier 
> versions), apache-2.0.61_2. I tried Lighttpd, which produces same problem.
>
> Same happens with AR::Reports::Transaction.
>
> Anyone knows how to fix this? My collegues already want to purchase a 
> commercial product because of this...(pastel partner) :-(
>
> Thanks,
> martin
Seems really strange error. Is this happening with all reports or just 
with these two?

Sometimes the left joins can take the database down for simple queries 
if there is no department/warehouse defined. But your testing does not 
point to database.

Which version of postgres? Try doing vacuumdb to the database

-- 
Purpose-built SQL-Ledger Hosting
http://www.ledger123.com/

Free trial available.
--

[SL] Timeout on AR::Reports::Outstanding

[Martin B. <boe...@gm...>]

AR::Reports::Outstanding::next should show me all outstanding invoices. But 
loading the page times out (it stays busy all time without displaying 
anything on all browsers).

If I stop the postgresql database server while waiting for the result I get 
the following error:

> DBD::Pg::st execute failed: server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> Error!
>
> SELECT a.id, a.invnumber, a.ordnumber, a.transdate,
> a.duedate, (SELECT sum(ac.amount)
> FROM acc_trans ac
> JOIN chart c ON (c.id = ac.chart_id)
> WHERE ac.trans_id = a.id
> AND ac.approved = '1'
> AND c.link LIKE '%_tax%') * 1 AS tax,
> a.amount, (SELECT SUM(ac.amount) * -1 * 1
> FROM acc_trans ac
> JOIN chart c ON (c.id = ac.chart_id)
> WHERE ac.trans_id = a.id
> AND ac.approved = '1'
> AND (c.link LIKE '%AR_paid%'
> OR c.link LIKE '%AR_discount%'
> OR c.link = '')) AS paid,
> a.invoice, a.datepaid, a.terms, a.notes,
> a.shipvia, a.waybill, a.shippingpoint,
> e.name AS employee, vc.name, vc.customernumber,
> a.customer_id, a.till, m.name AS manager, a.curr,
> a.exchangerate, d.description AS department,
> a.ponumber, a.warehouse_id, w.description AS warehouse,
> a.description, a.dcn, pm.description AS paymentmethod,
> a.datepaid - a.duedate AS paymentdiff,
> ad.address1, ad.address2, ad.city, ad.zipcode, ad.country
>
> FROM ar a
> JOIN customer vc ON (a.customer_id = vc.id)
> JOIN address ad ON (ad.trans_id = vc.id)
> LEFT JOIN employee e ON (a.employee_id = e.id)
> LEFT JOIN employee m ON (e.managerid = m.id)
> LEFT JOIN department d ON (a.department_id = d.id)
> LEFT JOIN warehouse w ON (a.warehouse_id = w.id)
> LEFT JOIN paymentmethod pm ON (pm.id = a.paymentmethod_id)
>
>
> WHERE a.approved = '1'
> ORDER by 4 ASC,2,17
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.


So it seems that the server was busy fetching an sql-select. However if I take 
this query and paste it manually into psql I __instantly__ get the result 
(256 rows), so I don't think it's a problem of the database. Also my database 
is very small - about 64kb tar-gzip.

I am using FreeBSD 6.2 with Perl 5.8.8 (base system installations) with:
p5-DBD-Pg-1.49, p5-DBI-1.60.1, Sql-ledger 2.8.11 (happend also in earlier 
versions), apache-2.0.61_2. I tried Lighttpd, which produces same problem.

Same happens with AR::Reports::Transaction.

Anyone knows how to fix this? My collegues already want to purchase a 
commercial product because of this...(pastel partner) :-(

Thanks,
martin

Re: [SL] Moving SQL Ledger from one System to another

[Luke <acc...@li...>]

Why don't you just create a test company for her on the office database =

server?  Let her work with that, like one of the test versions on =

sql-ledger's web site.

 On Tue, 29 Jan 2008, =

lh...@pa... wrote:

> See I already have a secure openvpn tunnel to the office.
> But my problem was letting her "try" things on the "live"
> data. That is why I wanted to bring the data from the office
> to the home. So that way she can play with the system and
> I do not have to worry about anything.
> =

> Now Do I have to do
> =

> create a blank database and restore the data.
> =

> psql -U sql-ledger -c "create database newdb;" template1
> psql -U sql-ledger newdb < backup.sql
> =

> with the backup file on the home system ?
> =

> And does "newdb" have to be the same name as the one from the store ?
> =

> Thanks
> =

> Steven L'Heureux
> =

> > Why not create a secure but remote login?
> > She can then enter anything she wants in the real database.
> >
> > Just remember to backup, preferably also remote (email to different
> > locations is a smart bet).
> >
> > Two databases in two locations sounds like an accident waiting to happe=
n..
> >
> > 2008/1/29, lh...@pa... <lh...@pa...>:
> >>
> >> Basicly it's just so she can learn how to input everything now.
> >> Not just her daily sales. All her expenses, reciepts and such.
> >> So I want to bring an up to date copy of her data home and
> >> import it there so she can do work on it so she does not mess
> >> anything up.
> >>
> >> Steven L'Heureux
> >>
> >>
> >> > On =B2=D0, 2008-01-29 at 09:29 -0500, lh...@pa... wrote:
> >> >> How and what is the prefered method for moving
> >> >> my SQL Ledger Data from my wife's work to her
> >> >> home office?
> >> >>
> >> >> Systems are using Fedora.
> >> >
> >> > One-time thing? If so, do System -> Backup -> Save to file, copy the
> >> > file to the other system, and do restore as explained in the manual.
> >> > That will back up the data base. You should probably tar up and copy
> >> > over the users/ directory.
> >> > --
> >> > Stuart Luppescu -=3D- slu .at. ccsr.uchicago.edu
> >> > University of Chicago -=3D- CCSR
> >> > =BA=CD=CA=B8=A4=C8=C3=D2=C6=E0=C8=FE=A4=CE=C9=E3 -=3D-    Kernel 2.6=
.23-gentoo-r3
> >> > There is no time like the present for postponing
> >> >  what you ought to be doing.
> >> >
> >> >
> >> >
> >> >
> >> >
> >> ----------------------------------------------------------------------=
---
> >> > 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: 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: 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
> >
> > !DSPAM:11,479f77a446224379617435!
> >
> >
> =

> =

> =

> -------------------------------------------------------------------------
> 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
>=20

Re: [SL] Moving SQL Ledger from one System to another

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

I suggest to start a new company named test and same user as in live db as a
user.
Then:

su postgres
psql test < backup.sql

login test

I use a test firm to try everything. From invoice numbering to reports, from
stock and inventory to year-end.
Feels safer that way, and if it works in test, the chances of ruining the
real maccoy are slim.

That way the test data is clearly markeds as such, test. Fine for testing
and employee training.

I sure hope nobody is tempted to copy over testdata to the real database.
Seems certifiable ;-)

2008/1/29, lh...@pa... <lh...@pa...>:
>
> See I already have a secure openvpn tunnel to the office.
> But my problem was letting her "try" things on the "live"
> data. That is why I wanted to bring the data from the office
> to the home. So that way she can play with the system and
> I do not have to worry about anything.
>
> Now Do I have to do
>
> create a blank database and restore the data.
>
> psql -U sql-ledger -c "create database newdb;" template1
> psql -U sql-ledger newdb < backup.sql
>
> with the backup file on the home system ?
>
> And does "newdb" have to be the same name as the one from the store ?
>
> Thanks
>
> Steven L'Heureux
>
> > Why not create a secure but remote login?
> > She can then enter anything she wants in the real database.
> >
> > Just remember to backup, preferably also remote (email to different
> > locations is a smart bet).
> >
> > Two databases in two locations sounds like an accident waiting to
> happen..
> >
> > 2008/1/29, lh...@pa... <lh...@pa...>:
> >>
> >> Basicly it's just so she can learn how to input everything now.
> >> Not just her daily sales. All her expenses, reciepts and such.
> >> So I want to bring an up to date copy of her data home and
> >> import it there so she can do work on it so she does not mess
> >> anything up.
> >>
> >> Steven L'Heureux
> >>
> >>
> >> > On 火, 2008-01-29 at 09:29 -0500, lh...@pa... wrote:
> >> >> How and what is the prefered method for moving
> >> >> my SQL Ledger Data from my wife's work to her
> >> >> home office?
> >> >>
> >> >> Systems are using Fedora.
> >> >
> >> > One-time thing? If so, do System -> Backup -> Save to file, copy the
> >> > file to the other system, and do restore as explained in the manual.
> >> > That will back up the data base. You should probably tar up and copy
> >> > over the users/ directory.
> >> > --
> >> > Stuart Luppescu -=- slu .at. ccsr.uchicago.edu
> >> > University of Chicago -=- CCSR
> >> > 才文と智奈美の父 -=-    Kernel 2.6.23-gentoo-r3
> >> > There is no time like the present for postponing
> >> >  what you ought to be doing.
> >> >
> >> >
> >> >
> >> >
> >> >
> >>
> -------------------------------------------------------------------------
> >> > 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: 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: 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
> >
> > !DSPAM:11,479f77a446224379617435!
> >
> >
>
>
>
> -------------------------------------------------------------------------
> 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
>
>

Re: [SL] Moving SQL Ledger from one System to another

[Bob G. <bo...@rc...>]

As long as she understands that it is just a training system at home and
the information she keys into her home system will NOT be imported back
into the office system (this is where the problems can occur..), just
set up the home system with a copy of the office system.

The temptation will be to 'save some keystrokes' and attempt to import
the newly keyed data in the home system back into the live office
system.

Good Luck

Bob G

On Tue, 2008-01-29 at 15:50 -0600, Adam Vandemore wrote:
> Another option which we do is create a new dataset in the existing SL 
> installation, then restore a current backup to the new dataset and then 
> have your new user use the test dataset.  Easy to update and restore if 
> there's a screwup and you've avoided running multiple installations of SL.
> > See I already have a secure openvpn tunnel to the office.
> > But my problem was letting her "try" things on the "live"
> > data. That is why I wanted to bring the data from the office
> > to the home. So that way she can play with the system and
> > I do not have to worry about anything.
> >
> > Now Do I have to do
> >
> > create a blank database and restore the data.
> >
> > psql -U sql-ledger -c "create database newdb;" template1
> > psql -U sql-ledger newdb < backup.sql
> >
> > with the backup file on the home system ?
> >
> > And does "newdb" have to be the same name as the one from the store ?
> >
> > Thanks
> >
> > Steven L'Heureux
> >
> >   
> >> Why not create a secure but remote login?
> >> She can then enter anything she wants in the real database.
> >>
> >> Just remember to backup, preferably also remote (email to different
> >> locations is a smart bet).
> >>
> >> Two databases in two locations sounds like an accident waiting to happen..
> >>
> >> 2008/1/29, lh...@pa... <lh...@pa...>:
> >>     
> >>> Basicly it's just so she can learn how to input everything now.
> >>> Not just her daily sales. All her expenses, reciepts and such.
> >>> So I want to bring an up to date copy of her data home and
> >>> import it there so she can do work on it so she does not mess
> >>> anything up.
> >>>
> >>> Steven L'Heureux
> >>>
> >>>
> >>>       
> >>>> On $B2P(B, 2008-01-29 at 09:29 -0500, lh...@pa... wrote:
> >>>>         
> >>>>> How and what is the prefered method for moving
> >>>>> my SQL Ledger Data from my wife's work to her
> >>>>> home office?
> >>>>>
> >>>>> Systems are using Fedora.
> >>>>>           
> >>>> One-time thing? If so, do System -> Backup -> Save to file, copy the
> >>>> file to the other system, and do restore as explained in the manual.
> >>>> That will back up the data base. You should probably tar up and copy
> >>>> over the users/ directory.
> >>>> --
> >>>> Stuart Luppescu -=- slu .at. ccsr.uchicago.edu
> >>>> University of Chicago -=- CCSR
> >>>> $B:MJ8$HCRF`H~$NIc(B -=-    Kernel 2.6.23-gentoo-r3
> >>>> There is no time like the present for postponing
> >>>>  what you ought to be doing.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>         
> >>> -------------------------------------------------------------------------
> >>>       
> >>>> 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: 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: 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
> >>
> >> !DSPAM:11,479f77a446224379617435!
> >>
> >>
> >>     
> >
> >
> >
> > -------------------------------------------------------------------------
> > 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
> >
> >   
> 
> 

Re: [SL] Moving SQL Ledger from one System to another

[Adam V. <amv...@gm...>]

Another option which we do is create a new dataset in the existing SL 
installation, then restore a current backup to the new dataset and then 
have your new user use the test dataset.  Easy to update and restore if 
there's a screwup and you've avoided running multiple installations of SL.
> See I already have a secure openvpn tunnel to the office.
> But my problem was letting her "try" things on the "live"
> data. That is why I wanted to bring the data from the office
> to the home. So that way she can play with the system and
> I do not have to worry about anything.
>
> Now Do I have to do
>
> create a blank database and restore the data.
>
> psql -U sql-ledger -c "create database newdb;" template1
> psql -U sql-ledger newdb < backup.sql
>
> with the backup file on the home system ?
>
> And does "newdb" have to be the same name as the one from the store ?
>
> Thanks
>
> Steven L'Heureux
>
>   
>> Why not create a secure but remote login?
>> She can then enter anything she wants in the real database.
>>
>> Just remember to backup, preferably also remote (email to different
>> locations is a smart bet).
>>
>> Two databases in two locations sounds like an accident waiting to happen..
>>
>> 2008/1/29, lh...@pa... <lh...@pa...>:
>>     
>>> Basicly it's just so she can learn how to input everything now.
>>> Not just her daily sales. All her expenses, reciepts and such.
>>> So I want to bring an up to date copy of her data home and
>>> import it there so she can do work on it so she does not mess
>>> anything up.
>>>
>>> Steven L'Heureux
>>>
>>>
>>>       
>>>> On $B2P(B, 2008-01-29 at 09:29 -0500, lh...@pa... wrote:
>>>>         
>>>>> How and what is the prefered method for moving
>>>>> my SQL Ledger Data from my wife's work to her
>>>>> home office?
>>>>>
>>>>> Systems are using Fedora.
>>>>>           
>>>> One-time thing? If so, do System -> Backup -> Save to file, copy the
>>>> file to the other system, and do restore as explained in the manual.
>>>> That will back up the data base. You should probably tar up and copy
>>>> over the users/ directory.
>>>> --
>>>> Stuart Luppescu -=- slu .at. ccsr.uchicago.edu
>>>> University of Chicago -=- CCSR
>>>> $B:MJ8$HCRF`H~$NIc(B -=-    Kernel 2.6.23-gentoo-r3
>>>> There is no time like the present for postponing
>>>>  what you ought to be doing.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>         
>>> -------------------------------------------------------------------------
>>>       
>>>> 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: 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: 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
>>
>> !DSPAM:11,479f77a446224379617435!
>>
>>
>>     
>
>
>
> -------------------------------------------------------------------------
> 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
>
>   


-- 
Adam Vandemore
Systems Administrator
IMED Mobility

Re: [SL] Moving SQL Ledger from one System to another

[<lh...@pa...>]

See I already have a secure openvpn tunnel to the office.
But my problem was letting her "try" things on the "live"
data. That is why I wanted to bring the data from the office
to the home. So that way she can play with the system and
I do not have to worry about anything.

Now Do I have to do

create a blank database and restore the data.

psql -U sql-ledger -c "create database newdb;" template1
psql -U sql-ledger newdb < backup.sql

with the backup file on the home system ?

And does "newdb" have to be the same name as the one from the store ?

Thanks

Steven L'Heureux

> Why not create a secure but remote login?
> She can then enter anything she wants in the real database.
>
> Just remember to backup, preferably also remote (email to different
> locations is a smart bet).
>
> Two databases in two locations sounds like an accident waiting to happen..
>
> 2008/1/29, lh...@pa... <lh...@pa...>:
>>
>> Basicly it's just so she can learn how to input everything now.
>> Not just her daily sales. All her expenses, reciepts and such.
>> So I want to bring an up to date copy of her data home and
>> import it there so she can do work on it so she does not mess
>> anything up.
>>
>> Steven L'Heureux
>>
>>
>> > On $B2P(B, 2008-01-29 at 09:29 -0500, lh...@pa... wrote:
>> >> How and what is the prefered method for moving
>> >> my SQL Ledger Data from my wife's work to her
>> >> home office?
>> >>
>> >> Systems are using Fedora.
>> >
>> > One-time thing? If so, do System -> Backup -> Save to file, copy the
>> > file to the other system, and do restore as explained in the manual.
>> > That will back up the data base. You should probably tar up and copy
>> > over the users/ directory.
>> > --
>> > Stuart Luppescu -=- slu .at. ccsr.uchicago.edu
>> > University of Chicago -=- CCSR
>> > $B:MJ8$HCRF`H~$NIc(B -=-    Kernel 2.6.23-gentoo-r3
>> > There is no time like the present for postponing
>> >  what you ought to be doing.
>> >
>> >
>> >
>> >
>> >
>> -------------------------------------------------------------------------
>> > 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: 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: 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
>
> !DSPAM:11,479f77a446224379617435!
>
>

Re: [SL] Moving SQL Ledger from one System to another

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

Why not create a secure but remote login?
She can then enter anything she wants in the real database.

Just remember to backup, preferably also remote (email to different
locations is a smart bet).

Two databases in two locations sounds like an accident waiting to happen..

2008/1/29, lh...@pa... <lh...@pa...>:
>
> Basicly it's just so she can learn how to input everything now.
> Not just her daily sales. All her expenses, reciepts and such.
> So I want to bring an up to date copy of her data home and
> import it there so she can do work on it so she does not mess
> anything up.
>
> Steven L'Heureux
>
>
> > On 火, 2008-01-29 at 09:29 -0500, lh...@pa... wrote:
> >> How and what is the prefered method for moving
> >> my SQL Ledger Data from my wife's work to her
> >> home office?
> >>
> >> Systems are using Fedora.
> >
> > One-time thing? If so, do System -> Backup -> Save to file, copy the
> > file to the other system, and do restore as explained in the manual.
> > That will back up the data base. You should probably tar up and copy
> > over the users/ directory.
> > --
> > Stuart Luppescu -=- slu .at. ccsr.uchicago.edu
> > University of Chicago -=- CCSR
> > 才文と智奈美の父 -=-    Kernel 2.6.23-gentoo-r3
> > There is no time like the present for postponing
> >  what you ought to be doing.
> >
> >
> >
> >
> >
> -------------------------------------------------------------------------
> > 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
> >
> > !DSPAM:11,479f3d5e136532958492736!
> >
> >
>
>
>
> -------------------------------------------------------------------------
> 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
>
>