have standard names for columns in the database.
for instance on order details a column is called ITEM and DESC, but in purchase order detail its called ITEMNO and ITEMDESC.
The list goes on and on.
by: francois t. | over a year ago | General Enhancements
Comments
totally agree but this should have all been started consistently from day 1, it's probably a bit late to get changed now.
Believe me I understand, I'm also a developer & architect of a software package. Maybe they can gradually make the change. It's really about best practices and naming convensions are the basics of it. It will really help people when we look at making report and database queries generic.
This is just bad development on their part. They should have looked at this problem a lot earlier. There are other database normality issues though and i think they need to revisit it in it's entirety...
I agree that naming convensions are the basics. It's almost as though they are just teasing us by making it over complicated and difficult to use.
It would be a pleasure to work with if they standardized the column names.
or where ITEMNO in one table is the formatted item number and in another table it is the unformatted item number...that one drives me insane!
And can we please make all the date and time fields be in MSFT SQL standard formats now that we only have one database to support?
can't even understand how it was architected this way in the first place but that's an entirely different conversation...again, sooner the better.