| Anonymous | Login | Signup for a new account | 2010-09-07 18:53 EEST |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ >> ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000013 | [qot] general | minor | always | 2009-02-08 13:15 | 2009-02-17 09:50 | ||||
| Reporter | philipp_t | View Status | public | ||||||
| Assigned To | administrator | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | resolved | Product Version | 0.0.4 | ||||||
| Summary | 0000013: unambiguous columns are not recognized - "unresolved identifier" | ||||||||
| Description |
Hi, found another small glitch (on the other hand, it already proposed some indizes I wasn't able to find out...great :-) ). If you specify a column that is unambiguous, MySQL will let you get away with it, but qot won't. Using your example tables "orders" and "clients" and running the following query qot --input-file=schema.sql --input-query="SELECT * FROM clients c LEFT JOIN orders o ON o.client_id = c.id WHERE first_name = 'zaphod';" --info results in the error message ERROR 65000001 at 'first_name': unresolved identifier though "first_name" could be resolved into a column of "clients". Thanks again, Philipp |
||||||||
| Additional Information | |||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
|
|
|||||||||
Notes |
|
|
(0000092) administrator (administrator) 2009-02-16 16:31 |
Thanks for the report! |
|
(0000096) administrator (administrator) 2009-02-17 09:50 |
The fix is pushed to lp:qot. |
| Mantis 1.1.1[^] Copyright © 2000 - 2008 Mantis Group |