Thank you for the provided information. I managed to reproduce the error you experience and was able to define a workaround for it.
Generally, the insertion of a database default GUID value in a primary key column in Oracle is a limitation on our side.
The alternative I would suggest to you is to use the GUID identity mechanism offered by Telerik OpenAccess ORM. This feature generates the GUID value for the primary key column of a given table instead of both the developer and the server. You can find more information about it in this documentation article
The implementation of the suggested workaround would require a small change in the design of the primary key column - its type should be varchar2 and the length should be extended with 8 symbols:
<primary_column_name> VARCHAR2(40) DEFAULT
If that is feasible to you, the solution includes the following steps:
1) Update the design of the column
2) Update the class in the model using the Update from Database
3) Select the class in Visual Designer and set the Identity Mechanism
property to Guid
4) Select the identity property of the class in Visual Designer and change its type from String to Guid
5) Save the .rlinq file
If you continue to experience this behaviour after applying the suggested solution, it would be very useful to provide us with a sample project that demonstrates it.
I am looking forward to your feedback.
OpenAccess ORM Q2 2013 brings you a more powerful code generation and a unique Bulk Operations support with LINQ syntax. Check out the list of new functionality and improvements shipped with this release.