If you design your database schemas such that, where possible, corresponding columns have the same names in all tables, and you do natural joins, the problem will basically go away. -- Darren Duncan
On 2015-03-16 9:16 AM, Drago, William @ CSG - NARDA-MITEQ wrote: > All, > > Some of my Select statements are pretty long and I'm starting to think it'd > be a good idea to always include table names of columns instead of just when > they are not unique. This would make the Select statements longer, but > perhaps easier to understand if the reader knows where each column is from. > > Any thoughts on this? I realize something like this can be highly subjective, > but I'm wondering if there's a generally accepted practice in the SQLite > world. > > Thanks, > -- > Bill Drago > Senior Engineer > L3 Narda-MITEQ<http://www.nardamicrowave.com/> > 435 Moreland Road > Hauppauge, NY 11788 > 631-272-5947 / William.Drago at L-3COM.com<mailto:William.Drago at L-3COM.com> > > > CONFIDENTIALITY, EXPORT CONTROL AND DISCLAIMER NOTE:This e-mail and any > attachments are solely for the use of the addressee and may contain > information that is privileged or confidential. Any disclosure, use or > distribution of the information contained herein is prohibited. In the event > this e-mail contains technical data within the definition of the > International Traffic in Arms Regulations or Export Administration > Regulations, it is subject to the export control laws of the U.S.Government. > The recipient should check this e-mail and any attachments for the presence > of viruses as L-3 does not accept any liability associated with the > transmission of this e-mail. If you have received this communication in > error, please notify the sender by reply e-mail and immediately delete this > message and any attachments. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
