ORM problem with special columnnames

[Richard Koslik]

Hello!

After two days of searching for an error, I found out that I should not use "SYS" as a part of a table- or columnname. My tablename was named "SYSP" and my primary key field "SYSP_S_KEY". If I changed data in the table and then called the function SubmitChanges I got the following error message: "key field not found". 
I have the same problem with my table "PROG" and I believe that I can solve it the same way ... if I rename my table to another name.

Also I found out that ORM has problems if my tablename ends with "S" like "TEXTS", then it has problems with it's automatically generated functions. Because the programm tries to add a small "s" and sometimes it works and sometimes not.

I have learned now:
- tablenames should not end with "S"
- don't use "SYS" in columnnames for primary keys
- dont' use "PROG" in columnnames

Now my question to you, are there more such KEY-words which make problems with ORM, if I use them as/in columnnames??? 


Best Regards,
Richard

[Jan Blessenohl]

Hi Richard Koslik,
We are not aware of such problems at the moment, OpenAccess delimits all table and column names which should not produce errors even with reserved words.

Can you explain a little more what you are doing? Are you using the old forward/reverse wizards or are you using the new UML-Like DSL designer? Which database backend are you using.

A small example showing the problem would be great to help us to fix such problems.

Best wishes,
Jan Blessenohl
the Telerik team

[Richard Koslik]

Hello I made a support call, because I am not able to attach a Code-File. (ticket ID is: 355146)

Best regards, Richard

[PetarP]

Hi Richard Koslik,

 We have verified and fixed the bug. The fix will be available in our next internal build that is scheduled for this week.

Greetings,
Petar
the Telerik team