I’m really confused about the arguments around this, being that things like apostrophes and hyphens have special meanings in databases.
Yes, they do… But there are incredibly mature standard practices around how to store and query this type of data so that it isn’t a problem.
Hyphens and apostrophes aren’t uncommon in surnames. Is anyone suggesting banning those?
Yes, please
"All punctuation will be considered but avoided where possible because street names and addresses, when stored in databases, must meet the standards set out in BS7666.
“This restricts the use of punctuation marks and special characters (e.g. apostrophes, hyphens and ampersands) to avoid potential problems when searching the databases as these characters have specific meanings in computer systems.”
This seems like a dumb line of reasoning. The problem has never been the signs or punctuation in a database. It’s that the people in charge don’t even know what BS7666 even says.
We have a piece of legacy software and we have to replace certain symbols in text values as there’s manual SQL construction everywhere and none of it uses parameters.
Ah, yes, I live on “St Mary’ ; DROP TABLE street”
“we call it Drop street for short”
I thought it’s the standard’s name that fits the situation, but it appears to be humans at a blame as usual
How did they ask all these random people and not bother to ask a single software engineer?
“Hi is this excuse real, or is it just a sign of an inappropriate relationship between the local council and a dodgy software company that pays more dividends than developers? Oh it’s the latter? Okay, thanks.”
Wait, is this about SQL injection? Are they admitting that If I paste a piece of paper that says
'; drop table streets; --over their street sign it’ll fuck all their shit up?If so, this is not a problem that should be fixed by changing the street signs.
Or is the problem that they’ve got people with limited technical skill manually constructing SQL queries to search these “geographical databases” and not knowing how to properly escape them?
Or did some intern developer neglect to use a parameterized query and something broke and the management chain at the North Yorkshire Council who don’t even know what pebkac stands for heard “apostraphies are the problem?”
Maybe they’ve got some image recognition thing on their mail trucks and the apostrophies mess up the otherwise-monospace letter spacing?
Whatever the case, the whole idea of taking the apostrophies off the signs seems ridiculous to me.
So North Yorkshire Council just announced to the whole world that its systems are vulnerable to SQL injection and it’s easier to replace the signs than to fix the software?
Time to upgrade their systems to support UTF8.
Can’t wait to live on 💩 🕳️ 🛣️.
Probably interpolated strings are used in their DB queries. But instead of fixing the code, it’s probably cheaper to fix the road-signs. Seems to me like they need to overhaul their IT system.
Half the yoofs in yorks, “picks up a screwdriver, whistling. " Off to grab some limited edition street signs lads”"
>
Good luck writing Yorkshire dialect without t ‘umble apostrophe, dick’eads
One of my favourite Yorkshire dialect jokes is how “tin tin tin” can mean the complete sentence “It isn’t in the tin”
“If you start losing things like that then everything goes downhill doesn’t it?”
Is this a joke? I wish, but I doubt it.
They have a point, though. It’s digital representation that should reflect real world, not the other way around.
In the same way I can totally imagine truncating street signs with names too long for a
char(16)field someone came up with when creating a DB. Reminds me of people making logistics software and limiting Zip codes to be 6 digits.In this case the digital representation reshapes the real world and that makes me uneasy and weird feeling for some reason
Edit: was meant to post to the post above yours
In this case the digital representation reshapes the real world and that makes me uneasy and weird feeling for some reason
And to think Butt Hole Road used to be in Doncaster
