need solution

[Chiranjeevi Kanthraj]

Hi all
i have developed an DataBase application in java.
my problem is if Data base table's schema is changed, and the code to access that data is not changed. the application is crashed.

i their any software to track this problems and it should inform the developer that table is modified, code is changed like that.

Thanks in advance

[Sagar Rohankar]

i their any software to track this problems and it should inform the developer that table is modified, code is changed like that.

No , i don't think there is any software like this, but you can always set the DB parameters when you start your application or set all DB information in .properties files and access those settings, so whenever your BD schema changes, you can reflect those changes in properties file .

Hope this help !!

[Scott Selikoff]

Originally posted by Chiru Raj:
i their any software to track this problems and it should inform the developer that table is modified, code is changed like that.

e-mail + a competent employee

[Chiranjeevi Kanthraj]

i did not get you

[Scott Selikoff]

I was trying to point out that I've never worked in an environment in which one employee was allowed to change the database schema without some process for notifying the development team. In fact, all database changes generally require notifying the development team. In some organizations, employees have to get permission from developers even before making the change.

In other words, the best 'automated' tool to inform the developer there's a change in the database is the individual who made the change.

[Chiranjeevi Kanthraj]

Ya you are right.

But its happened by mistake. So i want to know is their any thing to control or track.


Thanks for all these inputs

[Scott Selikoff]

Not really. I mean you could write a tool that compares one database structure against another but its kind of unnecessary. If you can't trust the people modifying the database, then they shouldn't be modifying the database in the first place. Really, this is a software developer training and process issue, not a code issue.