ORA-00904: Invalid identifier???

Discussion of open issues, suggestions and bugs regarding ODAC (Oracle Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
Kaus Media
Posts: 13
Joined: Tue 12 Sep 2006 10:02

ORA-00904: Invalid identifier???

Post by Kaus Media » Fri 13 Jul 2007 08:15

Hi,

I wanted to upgrade from 5.80 to 6.10 but now I get an error message when posting a record in a TSmartQuery I did not have before the upgrade (I did not change any source line...)

I have a TSmartQuery looking for data on a table and a view like this:

SELECT FAX.PAGES.ROWID,
FAX.PAGES.*,
FAX.PAGE_VERSION(FAX.PAGES.PAGE_ID) AS PAGE_VERSION,
FAX.V_PATIENTS.STUDY_LONG_DESCRIPTION,
FAX.V_PATIENTS.STUDY_SHORT_DESCRIPTION,
FAX.V_PATIENTS.CENTRE_SPONSOR_NAME,
FAX.V_PATIENTS.PATIENT_DESCRIPTION
FROM FAX.PAGES
LEFT JOIN FAX.V_PATIENTS ON FAX.V_PATIENTS.PATIENT_ID=FAX.PAGES.PATIENT_ID
ORDER BY FAX_IN_ID, FAX_PAGE

The updating table property is properly set on FAX.PAGES, but when posting, ODAC returns an error:
ORA-00904: "LEFT"."PATIENT_DESCRIPTION": Invalid identifier

I am using BDS2006 Architect, WXP SP2, ODAC 6.10
My bet is that ODAC 6.10 thinks my "LEFT JOIN" is a table name ;)

Thanks

Plash
Devart Team
Posts: 2844
Joined: Wed 10 May 2006 07:09

Post by Plash » Fri 13 Jul 2007 14:31

We could not reproduce this problem. But we have fixed some problems with detecting read-only fields in TSmartQuery. So that probably the problem that you have encountered has been fixed. This fix will be included in the next ODAC build.

If it is possible, send to odac*crlab*com a complete small sample that demonstrates the problem, including script to create server objects.

Kaus Media
Posts: 13
Joined: Tue 12 Sep 2006 10:02

Post by Kaus Media » Wed 18 Jul 2007 12:01

Weird...

I have tried to reproduce the trouble in a separate and new project, but indeed, no error showed up!?

Retried my project with 6.10 to be sure, and it was still bugging. So I just simply rolled back ODAC 5.80 and now... my project works just purrrrfect...

Sorry, I can't help any further. I will keep 5.80 for now and regularly check if new builds correct this issue as suggested.

Thanks.

Post Reply