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
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
