Re: Shared column name

2004-08-30 Thread Stuart Felenstein
Typist's cramp ? Can you say visual query builder. ;) Stuart --- [EMAIL PROTECTED] wrote: > You have to say which table's VendorID column you > want to evaluate your > WHERE clause against (just as the error message > says). Try this > > WHERE > (VendorJobs.`VendorID` = 13) > > As a shortcut

Re: Shared column name

2004-08-30 Thread SGreen
You have to say which table's VendorID column you want to evaluate your WHERE clause against (just as the error message says). Try this WHERE (VendorJobs.`VendorID` = 13) As a shortcut , and to keep you from getting "typist's cramp", you only _need_ to specify the table name for columns that

Re: Shared column name

2004-08-30 Thread Mark C. Stafford
Try specifying the source tables more explicitly in your SELECT statement. SELECT table_a.VendorJobs opt_a , table_b.VendorJobs opt_b ... -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

Re: Shared column name

2004-08-30 Thread Martijn Tonies
Hi, > I know what the deal is supposed to be but can't seem > to fix it. > Two tables, VendorID exists in both tables (neither > are primary keys) > > I'm getting a "VendorID in where clause is ambiguous" > Sometimes it actually processes the SQL weird. > I think this is because same column name in

Shared column name

2004-08-30 Thread Stuart Felenstein
Hi, I know what the deal is supposed to be but can't seem to fix it. Two tables, VendorID exists in both tables (neither are primary keys) I'm getting a "VendorID in where clause is ambiguous" Sometimes it actually processes the SQL weird. I think this is because same column name in both tabl