Apr 4, 2019 2:40 PM
thx4sharing1
2983
26
3
#funny #development #coding #sql #marriage
funny
development
coding
sql
marriage
ChromaticPassingTone
rollback;
condor07uk
Always use TRANACTIONs to make sure that wont be a problem
NapoleonTrousersnakeBonaparte
v
da1stjster
I guess coding is harder than anything else after all
BadPunsAplenty
Well, when you start with a UNION statement, the inserts don't happen as often.
PinbotWizard
And that's why Wife is temporary.
AddSomeContext
Unique constraint violation....
jtms
Always index first, it makes inserts take longer, but it’s better for later
IllogicalFalicy
Did you remember to define #wife before inserting?
Better #wife than ##wife where anyone has permissions.
That's some deeper level humor there.
Alternatively: alter database Wife set multi_user;
Yeah, you're already sharing her with anyone else who is SA when you're not actively connected anyways
At least multi user could be a good thing ;)
ChromaticPassingTone
rollback;
condor07uk
Always use TRANACTIONs to make sure that wont be a problem
NapoleonTrousersnakeBonaparte
da1stjster
I guess coding is harder than anything else after all
BadPunsAplenty
Well, when you start with a UNION statement, the inserts don't happen as often.
PinbotWizard
And that's why Wife is temporary.
AddSomeContext
Unique constraint violation....
jtms
Always index first, it makes inserts take longer, but it’s better for later
IllogicalFalicy
Did you remember to define #wife before inserting?
ChromaticPassingTone
Better #wife than ##wife where anyone has permissions.
IllogicalFalicy
That's some deeper level humor there.
ChromaticPassingTone
Alternatively: alter database Wife set multi_user;
IllogicalFalicy
Yeah, you're already sharing her with anyone else who is SA when you're not actively connected anyways
IllogicalFalicy
At least multi user could be a good thing ;)