OraFAQ Forum: General » Document Centric Design Issue

Home » Other » General » Document Centric Design Issue

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Document Centric Design Issue [message #124586]

Mon, 20 June 2005 06:46

jock
Messages: 3
Registered: June 2005
Location: iyguy

Junior Member

Hello,

I have a design issue. I am beginning development of a new database on Oracle 10g platform, I have all of Oracles utilities at my disposal (2 many probably).

Could anyone suggest the best method to develop a database that is "document centric". The client wants to be able to add new fields to existing tables in the future and a user mechanism for loading data to those new columns. (Aggh).

Thanks in advance for any feedback.

Rgds

Report message to a moderator

Re: Document Centric Design Issue [message #124851 is a reply to message #124586]

Tue, 21 June 2005 16:32

andrew again
Messages: 2577
Registered: March 2000

Senior Member

A common practice in applications like SAP and Oracle Apps. is to add a few general purpose "flex" fields of various data types to selected tables. You then populate a meta-data table to configure what lables, validations those columns will have on the UI. The normalized approach of adding additional rows to a child table to represent additional columns on a parent table can be really messy - especially when you try to reconstruct a logical view of the physical tables. It can be done using views, but if you want them to be updateable too then it's not so easy...

Report message to a moderator

Re: Document Centric Design Issue [message #124856 is a reply to message #124586]

Tue, 21 June 2005 18:09

William Robertson
Messages: 1643
Registered: August 2003
Location: London, UK

Senior Member

I might be missing something but I don't see what allowing end users to make ad hoc additions to your data model has to do with a Document-centric design, if there is even such a thing.

I don't think there is any substitute for having a data model in which thoughtfully named columns have a clear purpose and well understood properties. It's easy enough to add, modify, rename and drop columns in Oracle, and plenty of modelling tools to keep track of it all. Having a client app that presents column UDF_42 as "VAT Registration Date" is never as good as the real thing.

The flexibility to make changes later without having to pay consultants to think about it may understandably seem to the client like something well worth putting on the wish list - just be careful what you promise.

Report message to a moderator

Re: Document Centric Design Issue [message #124913 is a reply to message #124586]

Wed, 22 June 2005 05:47

jock
Messages: 3
Registered: June 2005
Location: iyguy

Junior Member

Thanks for your replies.

I have a solution

[Updated on: Thu, 23 June 2005 05:09]

Report message to a moderator

Re: Document Centric Design Issue [message #125032 is a reply to message #124913]

Wed, 22 June 2005 17:53

William Robertson
Messages: 1643
Registered: August 2003
Location: London, UK

Senior Member

Quote:

I have a parser which shall pick up changes to the document when invoked.

I'm afraid I have no idea what that means. What is a document? How does it change? Why does that affect the relational data model?

How is dropping and recreating a table any better than altering an existing table? What about all your stored PL/SQL? Oh, of course - all the logic will be in the client app, right?

Report message to a moderator

Previous Topic:	Using Perl to manipulate a text file of records and put in Oracle Database
Next Topic:	difference between oracle8,oracle8i and oracle 9i

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Nov 23 02:47:54 CST 2024