• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

your opinion of the most important part of database-based developing?

 
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
I think it's really a general question,perhaps not bound to JDBC only.
What would you guys consider to be the most important part of the whole process of the development of softwares based on database? I need your opinion please.
THX
--eliot
 
Ranch Hand
Posts: 1143
1
Eclipse IDE Oracle Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Understanding the business that you're developing the application for.
Good Luck,
Avi.
 
Bartender
Posts: 1844
Eclipse IDE Ruby Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
More specifically, understanding the data structures associated with that business and designing the database correctly.
Understanding the concept of database normalization is an important part of designing a database, and it is even more important to understand when you should "de-normalize" portions of your database. (This is not often recommended, but sometimes the business just doesn't do business in a fully-normalized situation, and that can cause unnecessary overhead in the form of DB I/O in an application.) Usually, however, the problem is that the database is not normalized enough (or not at all....)
Understanding how to design reports based off of the data in your database. Mostly, data is not useful unless it is reported back to someone somehow. Views are incredibly important here (don't de-normalize your database for reporting concerns! Use views instead)
Other concerns involve understanding how your application handles concurrent users and obtaining primary keys; these are more app-specific thatn DB-design specific, though.
 
reply
    Bookmark Topic Watch Topic
  • New Topic