fixed in fpc revision 4086 On Sun, 2006-07-02 at 16:18 +0200, Zlatko Matić wrote: > Yes, the same happens when using simple sql query such as "select * from > sometable;". > > ----- Original Message ----- > From: "johnf" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Sunday, July 02, 2006 3:16 PM > Subject: Re: [lazarus] problems with SQLdb components and Postgres > > > On Saturday 01 July 2006 23:32, Zlatko Matić wrote: > > Hi! > > > > Well, I agree it is a complex query:) But the same happens with very > > simple > > query such as "select * from batches_microbs;"... > > I have only default logging on Postgres enabled. Please, tell me which > > options in postgresql.conf should I enable in order to see detailed log > > information. > > Thanks, > > > > Zlatko > > > > P.S. Have you seen screenshots that I sent you directly on your e-mail? > > > > > > ----- Original Message ----- > > From: "johnf" <[EMAIL PROTECTED]> > > To: <[email protected]> > > Sent: Saturday, July 01, 2006 11:59 PM > > Subject: Re: [lazarus] problems with SQLdb components and Postgres > > > > On Saturday 01 July 2006 11:05, Zlatko Matić wrote: > > > ((results_microbs join batches_microbs on' > > > ' (((results_microbs.batch) =' > > > ' (batches_microbs.batch)))) join' > > > ' (departments join plants on' > > > ' ((departments.department =' > > > ' plants.department))) on' > > > ' (((batches_microbs.plant) =' > > > ' (plants.plant)))) > > > > Fairly complex joins! Did you turn on the logging in Postgres? What does > > the > > log report say? Have you attempted to simplify the SQL expression to > > determine where the break down occurs? Although, I have a few complex SQL > > expressions in my code I don't attempt to create joins within joins. > > > > Also I generally use sqlquery.add for the expression. I did not check the > > rest of the code because you suggested that you were returning the wrong > > data > > types (which means that the program sent a legal sql statement). You also > > suggested that your sql statement worked from pgAdminIII. So again I > > wonder what FPC is sending to Postgres? Check the log and see if what is > > being sent > > from FPC matches what pgAdminIII is sending. If they do match then I > > suggest > > we have a bug in FPC. The funny thing is I think the first thing that > > happens when a sql select is made is the table information (such as field > > type) is returned. > > > > John > > In postgres.conf I have turned on the following: > log_statement = true > log_timestamp = true > > No I have not seen your screenshots. I have my mail filtered. I'll check. > > Are you getting the same issues with a simple select statement such as > "Select > * from SomeTable" ? > > John > > _________________________________________________________________ > To unsubscribe: mail [EMAIL PROTECTED] with > "unsubscribe" as the Subject > archives at http://www.lazarus.freepascal.org/mailarchives > > _________________________________________________________________ > To unsubscribe: mail [EMAIL PROTECTED] with > "unsubscribe" as the Subject > archives at http://www.lazarus.freepascal.org/mailarchives > -- Met vriendelijke groeten,
Joost van der Sluis CNOC Informatiesystemen en Netwerken http://www.cnoc.nl _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
