- 3,715,657 Users
- 2,242,821 Discussions
- 7,845,481 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 467 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 416 SQLcl
- 42 SQL Developer Data Modeler
- 184.8K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 8 DevOps
- 3K QA/Testing
- 247 Java
- 5 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 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
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 10 Español
- 1.9K Japanese
- 2 Portuguese
dotnet ef database update - any affect on existing oracle tables unrelated to the application?

Hi,
new to .net ef core and using visual studio code
Looking at tutorial at
want to use against an existing oracle schema we have which hosts a variety of datawarehouse tables and want to make sure command below has no affect on these existing tables
dotnet ef database update
assume this command simply creates/updates tables required by the .net application in question rather than delete the entire database and recreate.
Could someone please confirm?
Also to use this against oracle table do we need to just install the ef core beta and change the appsettings.json file to below?
"ConnectionStrings": {
"DefaultConnection": "User Id=<schema>;Password=<pwd>;Data Source=<SID>;"
},
Thanks
Answers
-
Your existing tables should not be affected as you will hit an "ORA-00955: name is already used by an existing object" if you try to use DB migrations to create an object that already exists in the schema. That's a problem nonetheless as you will have to rename your class to something else or provide a different name to use. IMO, it adds unnecessary complication to your app when you can decide right from the beginning to provide a clean separation between two different apps using unrelated schemas. Besides possible naming conflicts, patching/upgrading one app's DB means upgrading both, which means testing both for the upgrade when only one DB may want the patch/upgrade.
To use Oracle EF Core, you can follow this tutorial and use the sample code:
https://github.com/oracle/dotnet-db-samples/tree/master/samples/dotnet-core/ef-core/get-started
-
Thanks for update.
What about if wish to use identity as in tutorial below - will we be able to just change appsettings.json as per below
"ConnectionStrings": {
"DefaultConnection": "User Id=<schema>;Password=<pwd>;Data Source=<SID>;"
},
-
Oracle EF Core hasn't certified with ASP.NET Core Identity specifically. We'll probably take a look after our first production release.
-
Thanks for update