> I suspect most users copy/paste anyway. Some forms disable the paste action in the second box to force you to type it again (to avoid copying an error).
github: naelyn
Coupling queries to the database (stored procedures) instead of to the code that uses them (inlined queries) seems like a recipe for deployment headaches. Especially if you're deploying new code (with new queries) every…
So you're recommending writing a stored procedure for this? SELECT COUNT(*) FROM tblposts
I don't agree with prefixing tables with "tbl" to distinguish them from views, but I do agree with the general notion of using the prefix for any "table-like" entity in a database. If you work with a growing codebase…
> I suspect most users copy/paste anyway. Some forms disable the paste action in the second box to force you to type it again (to avoid copying an error).
github: naelyn
Coupling queries to the database (stored procedures) instead of to the code that uses them (inlined queries) seems like a recipe for deployment headaches. Especially if you're deploying new code (with new queries) every…
So you're recommending writing a stored procedure for this? SELECT COUNT(*) FROM tblposts
I don't agree with prefixing tables with "tbl" to distinguish them from views, but I do agree with the general notion of using the prefix for any "table-like" entity in a database. If you work with a growing codebase…