T
teppo_55
Guest
Good morning. The arguments to coinsider are: Avoid shortening Easiness to read (in code we always write table name, like employee.description) Appertains to fields without relations (like description, startDate, endDate) ? Can/should we use field names without rerefence to table name ? ? What about rule of two-piece field name (employee.description vs. employee.descriptionText) ? Regards teppo --------------------------|-------------------- Teppo Määttänen____| TR-Tiimi Oy Consultant_________| Struerintie 1 teppo @ trtiimi.fi____| 30100 FORSSA int-358-50-5748 226 | www.trtiimi.fi --------------------------|-------------------- Lähettäjä: Peter Judge [mailto:bounce-pjudge@community.progress.com] Lähetetty: torstai 7. syyskuuta 2017 16.57 Vastaanottaja: TU.OE.General@community.progress.com Aihe: RE: [Technical Users - OE General] Column naming conventions? Update from Progress Community Peter Judge I agree with Julian. An child tables/relation should include the parent name though Benefits.EmployeeId View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse. This email has been checked for viruses by AVG antivirus software. www.avg.com
Continue reading...
Continue reading...