Skip to main content

A widely used standard for documenting normalized data structure


There are various standards for documenting normalized data structures,
developed by different organizations as structured formal methods. Generally
speaking, it really doesn’t matter which method one uses as long as everyone reading
the documents understands it. Part of the documentation will always include a
listing of the attributes that make up each entity (also known as the columns that
make up each table) and an entity-relationship diagram representing graphically the
foreign to primary key connections. A widely used standard is as follows:
■ Primary key columns identified with a hash (#)
■ Foreign key columns identified with a back slash (\)
■ Mandatory columns (those that cannot be left empty) with an asterisk (*)
■ Optional columns with a lowercase “o”
Understand Relational Structures 19
The BOOKS tables can now be described as follows:
Table BOOKS
#* ISBN Primary key, required
o Title Optional
\* Publisher Foreign key, link to the PUBLISHERS table
Table AUTHORS
#* Name Together with the ISBN, the primary key
#\o ISBN Part of the primary key, and a foreign key to the BOOKS table.
Optional, because some authors may not yet be published.
Table PUBLISHERS
#* Publisher Primary key
\o Address code Foreign key, link to the ADDRESSES table
Table ADDRESSES
#* Address code Primary key
o Street
o City
o State

Comments

Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.


Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…