Viewing 15 posts - 1,786 through 1,800 (of 59,099 total)
The mistake is using the generic ChatGPT for questions in SQL. This version of the chatbot IS a rookie. There is a version of CHATGPT trained specifically for programming...
--Jeff Moden
Change is inevitable... Change for the better is not.
ChatGPT is DANGEROUS. It always produces results that seem plausible but can be entirely wrong. If you are lucky, it just won't compile. If you aren't it may...
--Jeff Moden
Change is inevitable... Change for the better is not.
I copied and pasted just the phone number in question from the XML you posted and put it in the following code. The "special characters" are an ASCII 160... which...
--Jeff Moden
Change is inevitable... Change for the better is not.
It could also have a default like GETDATE() or some other non-null, non-blank fixed value. That's why I'm thinking that the folks that asked the question are the ones best...
--Jeff Moden
Change is inevitable... Change for the better is not.
More proof of what I was talking about for the "Readily Consumable Data" thing. Two other folks saw a pattern that I'd missed and could easily test their solutions...
--Jeff Moden
Change is inevitable... Change for the better is not.
Assuming the pattern in the sample data is actually representative of your production data, the following would be simpler and more efficient as it eliminates the need to unpivot,...
--Jeff Moden
Change is inevitable... Change for the better is not.
Given the column naming convention, I think there might be a simpler solution than using an EAV. This assumes that there are three sets of weights: PWT, PNT, and...
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 1,786 through 1,800 (of 59,099 total)