Tag Info

New answers tagged

0

Even though 10,000 rows are not a lot, I would go for a slightly different solution that will perform a lot better. Keep you master table the same: id, name. Create a new alias/search table: itemid, alias Create an index on the alias and a foreign key constraint on the itemid. Do not have a delimited list of aliases, rather have a row for each ...


2

A very basic answer would be to let the developer know what exactly they're working with without needing to assign aliases in the event more than one table is being used. For example, if you're joining posts on comments (I'm not familiar with WordPress but just as an example), and the posts table as well as comments table have the columns title, author, ...


4

There is more than one school of thought concerning the naming of columns or fields. One school of thought says that the name should express the intent of the data being conveyed even if that name is separated from the context where it is found. Thus, a name like post_date or another name like comment_date tells the reader not only that this is a date, ...



Top 50 recent answers are included