I have just joined an in flight project and find the lead data modeler has created a name value pair data model.
The reason given was flexibility of data model considering some records can have as many as 900 attributes. The .Net application team seem to be loving it, as they can code everything with very few tables in mind.
I feel the model is difficult to query, difficult to load and difficult to syndicate and in all likelyhood will suffer from poor performance. Also the data model can't be considered as a rich metadata repository and difficult to understand.
Even though readability doesn't affect the actual performance of SQL statements, good programming practice calls for readable code. Readability is especially important if you have multiple conditions in the WHERE clause. Anyone reading the clause should be able to determine whether the tables are being joined properly and should be able to understand the order of the conditions.
I was working on a Application using oracle forms,where i need to call a sql script file with dynamic schema (dynamic owner), so i need to pass the owner from the oracle forms,
I came with the following procedure:
Submitted by Marcin Moczyróg on Sun, 2005-12-25 18:01
The aim of this article is to describe the process of creating a user-defined aggregate function. Oracle 9i was used to prepare and test the function; some parts of the code may not work with Oracle versions older than 9i. This article gathers information that is needed to write the aggregate function in one place, and presents a clear step-by-step descripion of the process.
Submitted by Saikat Goswami on Sun, 2004-09-12 01:00
XML is everywhere. Whether you are an Oracle system administrator, a .NET developer, or a J2EE analyst, XML undoubtedly is something that you bump into. In this article, I attempted to give you the basics of what you need to know to jumpstart your understanding of XML.