By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Hi Brian, in response to your answer for the query of
leaving the data integrity to the DB
by creating foreign keys or managing them through the application logic, you answered DB integrity is the best option. But I wonder why Oracle's own E-Business Suite doesn't carry any integrity constraints across the whole suite! Oracle Applications manages everything by way of code and not imposing any constraints (I don't say there are no constraints, still there are but relatively few). What's your opinion on this?
Without knowing more about the product, I would tend to say that this is poor design. As I stated in my earlier response, leave the data integrity to the database. I have rarely seen a reason to code data integrity in the app with today's Oracle database. I am always leery of apps that do not have constraints in the database. For those systems, I make sure that any changes to the data are always done with the app, otherwise, I can easily bypass their data protection mechanisms.