Re: [Ledger-smb-users] Postgres Access Timing

2009-07-25 Thread Chris Travers
On Sat, Jul 25, 2009 at 11:25 AM, wrote: > > > > -Original Message- > From: Chris Travers > To: ledger-smb-users@lists.sourceforge.net > Sent: Sat, 25 Jul 2009 17:41 > Subject: Re: [Ledger-smb-users] Postgres Access Timing > > > > I don't know

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-25 Thread lrspares45
-Original Message- From: Chris Travers To: ledger-smb-users@lists.sourceforge.net Sent: Sat, 25 Jul 2009 17:41 Subject: Re: [Ledger-smb-users] Postgres Access Timing On Sat, Jul 25, 2009 at 2:24 AM, beamends wrote: On Fri, 2009-07-24 at 10:05 -0700, Chris

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-25 Thread Chris Travers
On Sat, Jul 25, 2009 at 2:24 AM, beamends wrote: > > On Fri, 2009-07-24 at 10:05 -0700, Chris Travers wrote: > > How are you determining the customer/vendor that was inserted as well > > as the part? > > > > The vendor is a set depending on which file is being processed. For now > anyway it's har

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-25 Thread beamends
Right chaps/chapesses - found it! I was using nextval('id'::regclass) for inserting parts and nextval('partsvendor_entry_id_seq'::regclass) for inserting to partsvendor because it seemed sensible. However, removing these two makes it all work wonderfully! Quite why it should have been ok f

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-25 Thread beamends
On Fri, 2009-07-24 at 10:05 -0700, Chris Travers wrote: > How are you determining the customer/vendor that was inserted as well > as the part? > The vendor is a set depending on which file is being processed. For now anyway it's hardcoded from looking at the vendor table with phppgadmin. I'm not

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-24 Thread Chris Travers
How are you determining the customer/vendor that was inserted as well as the part? On Fri, Jul 24, 2009 at 7:43 AM, beamends wrote: > > On Fri, 2009-07-24 at 09:01 -0400, Eric Lucas wrote: > > Richard: > > > > Is this injection part of an ongoing process or just a one-time import > > of data? >

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-24 Thread beamends
On Fri, 2009-07-24 at 09:01 -0400, Eric Lucas wrote: > Richard: > > Is this injection part of an ongoing process or just a one-time import > of data? > > If you're only going to do this once then you might want to try > importing the data by using a spreadsheet to construct the necessary SQL

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-24 Thread Eric Lucas
Richard: Is this injection part of an ongoing process or just a one-time import of data? If you're only going to do this once then you might want to try importing the data by using a spreadsheet to construct the necessary SQL INSERT statements. It will load slower than your program would load

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-24 Thread beamends
On Fri, 2009-07-24 at 12:39 +0100, beamends wrote: > On Thu, 2009-07-23 at 09:00 -0700, Chris Travers wrote: > > > > > > > Hmmm I don't think it would be a timing issue unless you are > > doing strange things. Do you have errors from the PostgreSQL log > > file? > > > > Best Wishes,

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-24 Thread beamends
On Thu, 2009-07-23 at 09:00 -0700, Chris Travers wrote: > > > On Thu, Jul 23, 2009 at 2:15 AM, beamends wrote: > Hi All, > not strictly a LSMB thing, but as the answer may be of > interest to > others here goes... (excuse the terminology, I'm not of the >

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-23 Thread lai
it seems like you would need transaction control. also, in you sql statement, there should be a clause that allows you to set a wait time for data control language (dcl) when encountered a locking issue. often, it is undesirable to have locking issues within an app. probably should start looking at

Re: [Ledger-smb-users] Postgres Access Timing

2009-07-23 Thread Chris Travers
On Thu, Jul 23, 2009 at 2:15 AM, beamends wrote: > Hi All, > not strictly a LSMB thing, but as the answer may be of interest to > others here goes... (excuse the terminology, I'm not of the dbase expert > persuasion) > > > I'm "injecting" data into Postgres using a C program via libpq. From the >

[Ledger-smb-users] Postgres Access Timing

2009-07-23 Thread beamends
Hi All, not strictly a LSMB thing, but as the answer may be of interest to others here goes... (excuse the terminology, I'm not of the dbase expert persuasion) I'm "injecting" data into Postgres using a C program via libpq. From the documentation it's not clear if the various functions check/wait