288 reputation
17
bio website dcisgoingtohell.com/?p=443
location
age
visits member for 3 years, 6 months
seen Dec 2 '11 at 2:21

Jan
21
awarded  Yearling
Oct
21
comment what is a good way to show mysql experience?
SQL "portfolio" tends to be about high use/production databases, with millions+ records. Syntax knowledge doesn't mean a lot if it doesn't perform well...
May
6
comment Proper syntax formatting for SQL?
Vendor-specific SQL does have a preference - Oracle assumes uppercase (or is it lowercase?) for table and column names unless you enclose in double quotes (which adds support for non ASCII).
May
6
comment Proper syntax formatting for SQL?
@Tom H: I agree - it's seldom I run into cases that require such commenting.
May
6
answered Proper syntax formatting for SQL?
Feb
24
comment Is a designer supposed to write CSS code?
It's more the realm of the designer
Feb
10
awarded  Citizen Patrol
Feb
6
comment Breaking into database administration
I recommend reading: brentozar.com/sql/how-to-get-a-junior-dba-job
Feb
6
comment Top bad practices in MySQL
@Thorbjørn Ravn Andersen: I've demonstrated that your desire lacks rational sense, going against common naming conventions. These conventions exist because people have run into the issue before, and hope to stop others from making the same mistake. Ignore them at the inconvenience to yourself when such issues arise, and to those who have to work in your codebase. When I see it in code reviews, I'm struck by how sloppy and amateur it is.
Feb
6
comment Top bad practices in MySQL
@Thorbjørn Ravn Andersen: Table or column, doesn't change the issue. Limit to what? What if you need to add another limit column/table -- can't have two of the same name, so what do you do? It's no different than variable, class (and method/function naming, depending on overloading support) naming. Your argument is pretty weak.
Feb
6
comment Top bad practices in MySQL
@Thorbjørn Ravn Andersen: LIMIT is too generic for use anyway. First question from anyone unfamiliar with the table/entity is going to ask "limit for what?" Differing between databases only matters if needing to support more than one -- not all projects do.
Feb
6
comment Top bad practices in MySQL
@Thorbjørn Ravn Andersen: Yes, but my point stands that people who name tables as such should learn not to. Blindly backticking everything is amateur, and they won't learn if they don't see the error to know why.
Feb
5
comment Top bad practices in MySQL
MySQL only allows one index per SELECT, and has a limited amount of space for indexes -- so I see a lot of difficulty satisfying your first bullet.
Feb
5
comment Top bad practices in MySQL
@gahooa: I don't understand the question, but here's the MySQL reserved keywords documentation. I don't know of any language that likes/allows the use of keywords/syntax for method/variable/etc naming.
Feb
4
comment Top bad practices in MySQL
@skurmedel: I'd substitute you with a small shell script :p
Feb
4
revised Top bad practices in MySQL
added 500 characters in body
Feb
4
comment Top bad practices in MySQL
@skurmedel: For you, I'd consult a thesaurus :p
Feb
4
comment Top bad practices in MySQL
Brackets imply order of operations, which is useless if there's only one criteria within. Formatting > brackets for readability. ANSI-89 syntax doesn't support OUTER joins, so use of ANSI-89 implies the user(s) don't know...
Feb
4
comment Top bad practices in MySQL
@Phobia: It's easier to read if syntax is in CAPS, and everything else is not. Read any of my answers on SO for example.
Feb
4
awarded  Teacher