CodeFluent Entities Oracle Producer is available (in Beta)!
This long awaited persistence layer producer is now available for our customers. So there are now two persistence producers available from us: Microsoft SQL Server (supporting versions 2000, 2005 and 2008), and Oracle Database (supporting versions 10 and 11).
The Oracle producer is very logically comparable to the SQL Server one, in terms of features. It is capable of generating SQL scripts for:
- Constraints (primary and foreign keys)
- Procedures (and associated Oracle Packages)
- Sequences (for auto numbering support)
- Instances (including CodeFluent blob objects)
The beta version of this producer is missing one cool feature though: the difference engine. Today, it drops and recreates tables at each generation. However, this can be mitigated by the use of CodeFluent Entities instances.
As a funny example, we have converted the Access Northwinds database into an SQL Server and an Oracle Northwinds database without writing a single line of code, using some cool CodeFluent Entities features.
This is an image of the original unmodified Access database:
The first action was to use the CodeFluent Entities Access Importer. This has created a CodeFluent Entities model, shown here using the CodeFluent Entities Portable Editor (not yet released!):
Then, we used simultaneously the SQL Server and the Oracle producer on the CodeFluent Entities model. This is a diagram of the generated schema shown in SQL Server Enterprise Manager:
And this is a screenshot of Oracle’s SQL Developer, displaying the generated database:
Although CodeFluent Entities is *not* an import/export tool, it does help for interoperability scenarios!
Some key points to emphasize:
- The process used here is not a “simple” database-to-database import. It is a database-to-model-to-database generation. Oracle or SQL Server are not aware about Access here. The model could be modifed to suit any needs.
- The CodeFluent Entities Access importer is capable of extracting Access OLE Objects and transforming them into CodeFluent Entities blob instances. Because SQL Server and Oracle producers are both capable of saving CodeFluent Entities instances, including blob instances, they are also imported into the generated databases. We can clearly check this in the last screenshot (using SQ Developer builtin blob/image visualization feature) showing an image blob that existed in the original Access database.
The Oracle producer is available in latest CodeFluent builds, starting from today, here “http://www.codefluent.com/builds/Latests/”
The documentation has not yet been updated for the Oracle producer, so if you need it, please contact us at email@example.com.
CodeFluent Entities R&D team.