Hello,

As Hibernate automatically creates tables based on our mapping, don't we need to design the database?
If we need, why?
also, which one we need to design first? should we desing database first or classes first?

Thanx in advance,
SSSS

That was a good link...but i want to know what is the best practice when we are starting a complete new application?

schema export (especially schema update) depends on jdbc driver quality
if you are sure you have a very good jdbc driver and you are going to model your app the oo way, start from java classes (after a good uml design).
if your team is more db oriented, well just make sure they build a non broken schema.

So...is there nothing like best practice for this? Does it only depend on whehter i have good class design team or good db design team?

i have just started writing an application. I know only the requirements...i have the liberty of designing classes and tables in a manner i like..but i have no clue where to start....what is the standard practice?

Database first or classes first or simultaneous?

As I am using Hibernate for the first time, i am a bit confused...
plz help...

Thanks,
SSSS.

This is a bit like asking is COBOL beter than Java better than C++. It all depends. There is nothing instrinsically making one better than the other. They all have strengths and weakness.

I understand that people new to a given subject like "black and white" and "this or that" type unequivocality. But questions like "best practice" in programming have, by nature, multiple "correct" answers.

Personally, I always grew the java domain model and database models in tandem. But I have a very strong database background and feel comfortable manually setting up database objects.

So in short, it depends. The best answer is probably which ever way you feel most comfortable.