Database auditing can be a crucial component of database security and compliance with government regulations. Database auditing helps to answer questions like “Who accessed or changed data?” and “When was it actually changed?” and “What was the old content prior to the change?” Your ability to answer such questions can make or break a compliance audit. Sometimes it may be necessary to review certain audit data in greater detail to determine how, when and who changed the data.
The objective of this paper is to present the Whitemarsh approach to the definition of function points within database-centric business information systems, the process of counting function points, and the use of two metrics derived from function point counts to accomplish business information system estimating.
In this Mastering Grails installment, Scott Davis explores the various ways that Grails can use database tables that don't conform to the Grails naming standard. If you have Java™ classes that already map to your legacy databases, Grails allows you to use them unchanged. You'll see examples that use Hibernate HBM files and Enterprise JavaBeans 3 annotations with legacy Java classes.
One pattern that shows up repeatedly is creating a Many-to-Many relationship using a mapping class. In Rails, the hasMany/through directive provides this functionality. Grails doesn't have an explicit hasMany/through statement like Rails. Rather, Many-to-Many relationships are created implicitly by GORM via your domain classes.
Part 1 of this two-part article covers the basics of achieving a consistent, concise domain model and persistence tier with modern object-relational mapping (ORM) tools. In Part 2, the authors describe base domain entities, behavior in the domain model, and more-advanced features of a generic DAO. They also share strategies for enhancing data-retrieval performance with the domain model.
Although many developers use object-relational mapping (ORM) tools for their applications' persistence tier, some are confused about how to use them and duplicate code unnecessarily. The authors' experience constructing many persistence tiers has given them a clear understanding of persistence patterns and best practices. The first part of this two-part article covers the basics of a consistent, concise domain model and persistence tier. Part 2 builds and expands on the concepts covered in this article.
If you're a Java™ 2 Enterprise Edition (J2EE) developer, you'll want to preview the SQLXML technology. Check out procedures to create an XML document, store an XML document in a relational database, retrieve an XML document from a database, and navigate an XML document with the SQLXML Java data type.
When should an application use an embedded object database? Or, more precisely, when should a developer consider an embedded object database as an alternative to the more popular (and, probably, more familiar) relational database? This question is really two questions combined. The first is: when is it appropriate to use an ODBMS? The second is: assuming that you have determined to use an ODBMS, when is it appropriate to use an embedded one? (Many of the ODBMS systems mentioned above are available in both client/server and embedded forms.) In this article, I will deal with the individual, component questions separately. The combined answers will be the reply to the original question.