thanks for your help
11 Answers, 1 is accepted
with the next release, OpenAccess will contain a framework to allow such types to work. The framework can be used to perform mappings to your own UDT or to existing, predefined types (like MDSYS.SDO_GEOMETRY or Microsoft.SqlServer.Types.SqlGeometry) .
In fact, I've just verified if works with SDO_GEOMETRY and SqlGeometry and was able to store/retrieve persistent fields of such type.
Kind regards & stay tuned,
the Telerik team
will you support transaction when using sdo_geometry in oracle ? I am asking this question because in 10gR2 each time we handle a sdo_geometry oracle creates temporary table and the distributed transaction does not work anymore (but i know how you handle the transaction in openaccess though)
sebastien
I was not aware there is a transaction issue with SDO_GEOMETRY. How do I detect such a behavior?
We are storing such values within the scope of our normal transaction.
Thomas
the Telerik team
sdo_geometry cant be inside a TransactionScope, anyway i will see the open access feature when it comes.
thanks for answers.
sebastien
Hello
Sdo_geometry is
potentially a large amount of data (as a CLOB column in a database)
Does open access
support lazy loading for a property so that all the table is loaded except a
specific column into a class ? And once this property is called the geometry is
loaded.
Thanks for your answer.
sebastien
yes, this is done lazily, but can be forced also immediately depending on your application needs.
An SDO_GEOMETRY column would be lazy per default, an BIGINT column would be immediately per default.
Thomas
the Telerik team
I'm very interesting too to use SDO_GEOMETRY Oracle data type.
I would like to know if it is possible in Open Access to call an Oracle Package inside an sql request.
Exemple :
Open Access generate this kind of sql request : (Table is AMU and column is ID(number), CODE(varcahr2) and GEOMETRY(SDO_GEOMETRY)
select a."ID", a."CODE", a."GEOMETRY" from AMU.
I would like to produce this :
select a."ID", a."CODE", ASWKT(a."GEOMETRY) from AMU
ASWKT is a package that convert SDO_GEOMETRY to string so it can be retrieve by most of Oracle Provider.
Thanks
Julien
I did provide you with an example of how to work with SDO_GEOMTRY columns via your support ticket - 375127. As mentioned in that reply it is not possible to alter the 'select' sql and inject your package.
Do get back in case you need further assistance.
Best wishes,
Ady
the Telerik team
Can you provide an example of using SDO_GEOMETRY with OpenAccess¿?
Thanks in advance!
I have converted this ticket from a 'Forum' to a 'Products Feedback' in order to be able to send you the example. The example uses the Fluent API to map the field to a SDO_GEOMETRY column.
Hope this helps.
Kind regards,
Ady
the Telerik team