|
|
IMO, if this is how you behave, he should take it as a blessing that you are no longer involving yourself.
I suggest that you use your intelligence to take a look at your behaviour, and seek out "syntax changes" that will make it functional.
BTW, this is not a discussion. I have said what needed to be said, and will not visit this thread again.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
When you write your insert statement, don't attempt to insert a value into the fields that have identities set. Identities are automatically created for you by the database server. If you want to get the value that you created back, you simply use
SELECT Scope_Identity() AS CreatedIdentity immediately after the insert.
|
|
|
|
|
I know I shouldn't, but I just had to upvote that.
|
|
|
|
|
Hell I shouldn't of even posted it! But, I only have so much patience and I've tried asking him for more detail so many times and gotten nothing but a blank stare back.
|
|
|
|
|
|
I think It is using GUIDs as the identity column.
GUIDS have hyphens and I 'ont whant no mur hypens.
|
|
|
|
|
Actually GUIDs have no hyphens (these are numbers after all), it just happened that we mostly display it such way to help our eyes...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
But, when you query the DB (SQL Server) you get a value back for your (uniqueidentifier) identity which looks like:
BF5B2C5A-8E79-4FA0-8510-B3FD6BC819D6 (uniqueidentifier)
Right? So if you then try to do something with that value you would have hyphens and I was thinking that is what was hanging him up?
|
|
|
|
|
Yes, SQL - and others too - turn GUID into string...
If you read the RFC[^] you will understand why, but after all GUID is a 128 bit number...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: but after all GUID is a 128 bit number
Agree 100%.
Was just speaking about hyphens in this case with Guid identities in SQL.
|
|
|
|
|
Read the guidlines: "Insults, slap-downs and sarcasm aren't welcome. Let's work to help developers, not make them feel stupid.. "
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Yeah, yeah, I know them.
I'm allowed to lose my cool every now and then.
|
|
|
|
|
Before you can lose something, you must have it first.
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Developers have to first help others to help them.
This guy just isn't doing that and, much as profanity is (usually) unwelcome here, he deserved his put-down IMO.
|
|
|
|
|
"When I was 5 years old, my mother always told me that happiness was the key to life. When I went to school, they asked me what I wanted to be when I grew up. I wrote down 'happy'. They told me I didn't understand the assignment, and I told them they didn't understand life." - John Lennon
|
|
|
|
|
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Are you talking about a Guid here? Do you want to remove the hyphen from a Guid? You can convert the Guid to a string and replace the - with "" to remove the hyphen.
|
|
|
|
|
|
Sweet. That's what I learned today.
Regards,
Rob Philpott.
|
|
|
|
|
So?
public string ToString("N")
|
|
|
|
|
|
|