SQL Error

Apr 4, 2019 2:40 PM

thx4sharing1

Views

2978

Likes

26

Dislikes

3

#funny #development #coding #sql #marriage

funny

development

coding

sql

marriage

I guess coding is harder than anything else after all

6 years ago | Likes 2 Dislikes 0

rollback;

6 years ago | Likes 3 Dislikes 0

And that's why Wife is temporary.

6 years ago | Likes 2 Dislikes 0

Unique constraint violation....

6 years ago | Likes 4 Dislikes 0

Always use TRANACTIONs to make sure that wont be a problem

6 years ago | Likes 2 Dislikes 0

Always index first, it makes inserts take longer, but it’s better for later

6 years ago | Likes 3 Dislikes 0

Well, when you start with a UNION statement, the inserts don't happen as often.

6 years ago | Likes 10 Dislikes 0

Did you remember to define #wife before inserting?

6 years ago | Likes 3 Dislikes 0

Better #wife than ##wife where anyone has permissions.

6 years ago | Likes 3 Dislikes 0

That's some deeper level humor there.

6 years ago | Likes 1 Dislikes 0

Alternatively: alter database Wife set multi_user;

6 years ago | Likes 1 Dislikes 0

Yeah, you're already sharing her with anyone else who is SA when you're not actively connected anyways

6 years ago | Likes 1 Dislikes 0

At least multi user could be a good thing ;)

6 years ago | Likes 1 Dislikes 0