Home > Oracle Database > Oracle And The 30 Characters Limit

Oracle And The 30 Characters Limit


CodeFluent users define their business logic in a platform independent model where each concept will be translated into an actual component by what we call producers and which are basically code generators.

Therefore the business logic is decoupled from technical aspects, even though it’s still possible to include platform specific stuff in your model if you need to.

However, the targeted platforms have their limitations such as Oracle supporting identifiers up to 30 characters in length. So what happens if I define a 40 character long entity?

Well the Oracle Producer will automatically take care of it: the corresponding table identifier will be trimmed-down to a unique 30 characters long identifier. The same logic applies to all identifiers (columns, stored procedures, views, etc.), so that you can model your application regardless of the underlying technology, while at the same time, if needed, you still can define platform specific stuff in your model like a PL-SQL stored procedure for instance.

This way your model is freed from such limitations, and if later on you want to change your persistence layer implementation from Oracle to SQL Server or vice versa, switch your producers and you’re good to go 🙂

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s