O$8.0.3 plus Postgres 9.3 and 9.1
Good point Greg. In my app however, ALL column names are unique, so that
is a problem that has never arisen.
Cheers and thanks for the interest.
On Fri, Sep 8, 2017 at 11:12 AM, Grzegorz (Greg) Pasternak < firstname.lastname@example.org> wrote:
> Just a quick comment, I would advise to always fully qualify column names
> in your LEFT JOIN clause to avoid any ambiguity and consequently errors.
> On Sep 7, 2017, at 9:37 PM, Mike Rowan <email@example.com> wrote:
> > The following slightly simplified query in which iCol1, iCol5 are as
> > follows:
> > iCol1 integer 64 bit
> > iCol5 character simple char 1
> > —————————————————————–
> > SELECT @[iCol1] AS ref, @[#S1], @[iCol5]
> > FROM company, branch, purchaseorder
> > LEFT JOIN contact ON (ct_id = po_ct_id)
> > WHERE
> > co_id = br_co_id
> > AND br_id = po_br_id
> > AND po_invoice_nr >= 10000000
> > AND po_invoice_nr <= 10000100 AND ((po_type = 1) OR (po_type = 3)) > > ORDER BY po_invoice_nr
> > LIMIT 20000
> > ———————————————————-
> > results in this Error message:
> > ERROR: could not determine data type of parameter $2
> > As I am fairly new to SQL I’m not sure what is wrong. If I omit all
> > in the SELECT line except the first, there is no error. Any second or
> > term results in the same error.
> > Anyone got a minute for this one?
> > Mike
> > _____________________________________________________________
> > Manage your list subscriptions at lists.omnis-dev.com
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com