- 3,727,836 Users
- 2,245,473 Discussions
- 7,853,057 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 380.8K All Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.4K Databases
- 687 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 32 Multilingual Engine
- 499 MySQL Community Space
- 10 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 424 SQLcl
- 69 SQL Developer Data Modeler
- 185.2K SQL & PL/SQL
- 21.1K SQL Developer
- 2.7K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.9K Development Tools
- 18 DevOps
- 3K QA/Testing
- 387 Java
- 16 Java Learning Subscription
- 14 Database Connectivity
- 72 Java Community Process
- 3 Java 25
- 14 Java APIs
- 141.2K Java Development Tools
- 15 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 18 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 157 LiveLabs
- 36 Workshops
- 12 Software
- 6 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 17 Español
- 1.9K Japanese
- 4 Portuguese
ODP UDT Future on .NET core
Hello,
We are migrating a high profile .NET web app to .NET core. We are on Oracle(12c) EBS. All I/O is via stored procs with UDT parms. There are 100's of nested UDTs.
According to a scattering of info on here, twitter, & https://github.com/oracle/dotnet-db-samples/issues/56 UDTs are not yet available for the managed .NET ODP for .NET Core.
- What is the potential availability of this (earliest and latest estimates)?
- What advice do you have for migrating to .NET Core while continuing to use UDTs?
- Would this work:
- Continue (temporarily) to use existing .NET 4 services project that retrieves UDTs via current unmanaged ODP. (so no change)
- Build new .NET web project on .NET Core.
- Build new .NET class library project using .NET Standard. Migrate UDT classes from the .NET 4 services proj and make them POCO's (so trip out all the Oracle-specific references that wont work of course on .NET Standard). Then in the .NET 4 services proj, manually pass the UDT classes to the POCO's, where the POCO's will also be reference/available in .NET Core.
- Would this work:
Thanks! Any advice would be appreciated!
Best Answer
-
I'll have a better idea on the timing of managed ODP.NET and ODP.NET Core UDTs in a few months. The dev team is making good progress on the project.
Some customers who want to move now to managed or Core have converted to using well-known text geometries if they are using Spatial types..
Unmanaged ODP.NET does not work in .NET Core. So #2 is out of the question. #1 and #3 are possible.
Answers
-
I'll have a better idea on the timing of managed ODP.NET and ODP.NET Core UDTs in a few months. The dev team is making good progress on the project.
Some customers who want to move now to managed or Core have converted to using well-known text geometries if they are using Spatial types..
Unmanaged ODP.NET does not work in .NET Core. So #2 is out of the question. #1 and #3 are possible.
-
The above was not 3 separate solutions, but 1 solution consisting of 3 projects where #1 & #3 reference #2 (.net standard) The purpose of #2 (.net standard) was to place the POCOs & shared resources is all.
These are not spacial types so WKT is out.
It sounds like we will try with the above.
If you are not able to provide a SWAG estimate, I assume that this won't drop until 2021?
Thanks!
-
2021 would be the earliest possible delivery date. Harder to provide a more precise range until we make further progress.