Timeline for About my database date datatype crusade: Valid? Worthwhile? Does anyone else feel it?
Current License: CC BY-SA 3.0
22 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2021 at 8:50 | vote | accept | Caius Jard | ||
| Sep 13, 2017 at 10:23 | history | tweeted | twitter.com/StackSoftEng/status/907912722695811077 | ||
| Sep 7, 2017 at 2:21 | comment | added | Stack Exchange Broke The Law | "Don't be silly, we don't need to put ' when searching int" just tells you they don't like keystrokes that aren't strictly necessary, which means they hate your solution even more. | |
| Sep 6, 2017 at 16:20 | comment | added | Robert Harvey | People who use stuff from the Internet are responsible for making sure that whatever they use makes sense in their particular situation. It's not up to us to make sure their quoted strings are interpreted correctly, and I've worked with enough "bondage and discipline" languages to know that there's only so much you can do to protect people from themselves. You can install all the safeties and blade guards you want, but at the end of the day they still need to know how to use that saw properly. | |
| Sep 6, 2017 at 16:17 | history | edited | Robert Harvey | CC BY-SA 3.0 | edited body |
| Sep 6, 2017 at 14:31 | comment | added | Robbie Dee | Life is about picking your battles. In my view, this one just isn't worth fighting... | |
| Sep 6, 2017 at 13:47 | comment | added | JimmyJames | TL;DR but in production systems, I would expect dates like this to almost always be in parameters. Hardcoding dates into queries is a bigger problem than whether you use implicit conversions. If I'm writing some throw away query, it either works or it doesn't. I never do this anyway (because I can never remember the default date format) but I'm not sure it matters much. | |
| Sep 6, 2017 at 13:00 | answer | added | Becuzz | timeline score: 3 | |
| Sep 6, 2017 at 10:42 | comment | added | Thomas Owens♦ | I removed a question that is off-topic here - we don't do resource requests. One of the 2 close votes was given for this reason. Otherwise, I think this is a valid question, although it might border on being too broad. I hope that the removal of the off-topic question helps to narrow things down a little. | |
| Sep 6, 2017 at 10:41 | history | edited | Thomas Owens♦ | CC BY-SA 3.0 | deleted 808 characters in body |
| Sep 6, 2017 at 9:40 | answer | added | JacquesB | timeline score: 6 | |
| Sep 6, 2017 at 9:37 | answer | added | Phill W. | timeline score: 2 | |
| Sep 6, 2017 at 9:27 | history | edited | Caius Jard | CC BY-SA 3.0 | edited title |
| Sep 6, 2017 at 9:10 | history | edited | Caius Jard | CC BY-SA 3.0 | added 668 characters in body |
| Sep 6, 2017 at 8:52 | comment | added | Caius Jard | I did think about extending my example to ask whether WHERE age = '0x0F' is a valid way to hope a database will search for fifteen year olds.. | |
| Sep 6, 2017 at 8:50 | history | edited | Caius Jard | CC BY-SA 3.0 | added 668 characters in body |
| Sep 6, 2017 at 6:56 | review | Close votes | |||
| Sep 13, 2017 at 3:02 | |||||
| Sep 6, 2017 at 6:51 | answer | added | Doc Brown | timeline score: 8 | |
| Sep 6, 2017 at 6:16 | comment | added | Steve Barnes | I have even seen someone getting problems with WHERE datecolumn = 01/02/12'` where it is possible they are asking for the year 1912, 2012, 2001, 1901, 12 or 1. It is also a problem outside of the database world, the number of programmers who can't understand why converting "09" to an int is causing a crash are legion, 9 is not a valid octal digit and a leading 0 makes the string octal in a lot of systems | |
| Sep 6, 2017 at 6:10 | history | edited | Caius Jard | CC BY-SA 3.0 | added 350 characters in body |
| Sep 6, 2017 at 6:04 | history | edited | Caius Jard | CC BY-SA 3.0 | added 350 characters in body |
| Sep 6, 2017 at 5:58 | history | asked | Caius Jard | CC BY-SA 3.0 |