MySQL Tip of the day

[Spetnik]

Typing "2070" instead of "2010" will seriously screw up results that are sorted by date.

[mendhak]

Typing ALTAR TABLE will not work - it's either an ALTAR or a TABLE, it can't be both.

[Spetnik]

We should write a book

[wossname]

Typing "2070" instead of "2010" will seriously screw up results that are sorted by date.

Wishing your life away? Sounds like a cry for help.

[I_Love_My_Vans]

The command drop cascade is NOT your friend.

Was my first major cock up as a developer... well, that and not keeping a backup of my schema *D'oh!*

[abhijit]

You could have delegated the schema backup to the DBA.

[abhijit]

I think I coined another programming term.

"A cock-up": The error that results in the feeling that database and system administrators get. As in, the file deletion resulted in a major cock-up error for the windows admin.

[TheBigB]

Don't use VARCHAR(5) for storing booleans...

[NeedSomeAnswers]

'A cock-up' though is a general term when someone messes up, how is it also a programming term ?

[mendhak]

The command drop cascade is NOT your friend.

Was my first major cock up as a developer... well, that and not keeping a backup of my schema *D'oh!*

It's an oversight, though. On one hand, you forget it's there and you do 'something' which cascades. OTOH it isn't there and you end up having to perform several transactions to remove related records out of a DB.

What's better? I like the option with more control...

[GaryMazzone]

Drop cascade and Delete cascade you be removed from the ANSI standard. Any professional DBA (even developer) would never allow them to be used in code on a database.

[abhijit]

'A cock-up' though is a general term when someone messes up, how is it also a programming term ?

You're quite right, but look at the definition I coined in my other thread.

[mendhak]

Drop cascade and Delete cascade you be removed from the ANSI standard. Any professional DBA (even developer) would never allow them to be used in code on a database.

Wut u say? not understnading.

[abhijit]

Drop cascade and Delete cascade you be removed from the ANSI standard. Any professional DBA (even developer) would never allow them to be used in code on a database.

You are being facetious, right?

[GaryMazzone]

NO... I really believe that Delete and Drop Cascades should never be allowed to be used in a database.

[MaximilianMayrhofer]

I'd slam you for your incompetence, but it would probably garner the same satisfaction as winning a 'dunk the retard' contest.

[NickThissen]

Another tip:

Don't copy/paste a query a large number of times before testing it. I wrote "SELECT * FORM" instead of "FROM" by accident once and copied that like 50 times throughout a project. Then I used Replace All to replace FORM with FROM, not realizing half the table names contained the word 'FORM'.

[mendhak]

NO... I really believe that Delete and Drop Cascades should never be allowed to be used in a database.

They're good in the sense that you're maintaining relationships and the integrity of those relationships. It's sort of like a patriarchal nihilistic/fatalist society - if a guy dies, then the wife, children and dog must kill each other. It's convenient in the sense that the police don't need to go around and do it, they just do it themselves.

[NeedSomeAnswers]

They're good in the sense that you're maintaining relationships and the integrity of those relationships. It's sort of like a patriarchal nihilistic/fatalist society - if a guy dies, then the wife, children and dog must kill each other. It's convenient in the sense that the police don't need to go around and do it, they just do it themselves.