Database First,Object First?

		Wrox Programmer Forums > Java > Java and JDK > J2EE
Database First,Object First?

J2EE General J2EE (Java 2 Enterprise Edition) discussions. Questions not specific to EE will be redirected elsewhere.

Welcome to the p2p.wrox.com Forums.

You are currently viewing the J2EE section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com

October 26th, 2005, 01:28 AM

yinzhg

Registered User

Join Date: Oct 2005

Posts: 2

Thanks: 0

Thanked 0 Times in 0 Posts

Database First,Object First?

When we design a MIS Application,which is right?
1.Design the database table first,then design the data object
2.Design the data object according to business logic,then use some O/R Mapping tools to generate the databse table
3.design the databse table and data object in the same time

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Database or object is read-only	ryanb	Access ASP	25	January 17th, 2014 06:36 PM
Database First,Object First?	yinzhg	Hibernate	3	September 30th, 2007 01:41 AM
Accessing Object of Database	Sheraz Khan	ASP.NET 2.0 Professional	0	August 27th, 2007 10:30 PM
Can't DIM database object	egolsen	Access VBA	2	September 26th, 2005 04:25 PM
Database Connection Object	mrideout	BOOK: Beginning ASP.NET 1.0	4	August 3rd, 2004 07:42 AM