uncleflo
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 1 bookmarks
howto information development guide reference administration design website software solution service online product business uk tool company linux code server system application web list video marine create data experience tutorial description explanation learn technology build article blog world boat project download windows lookup security free performance javascript technical london control network beautiful tools support course file research purchase image library programming youtube example php construction opensource install community html quality profile computer feature power browser music platform mobile process work manage professional user share database hardware buy industry internet dance advice developer installation search 3d camera access customer material travel money test standard develop css review documentation engineering photography webdesign engine device digital speed api source event question program management client phone discussion story water simple content marketing yacht app account setup idea interface package fast communication cheap compare script market study easy live google resource operation demonstration startup monitor
Tag selected: avoiddatabase.
Looking up avoiddatabase tag. Showing 1 results. Clear
Why MySQL’s (SQL) DATETIME can and should be avoided
Saved by uncleflo on February 22nd, 2015.
MySQL, among other databases, has a column type called DATETIME. Its name seems to mislead people into thinking that it’s suitable for storing time of events. Or suitable for anything. This is a general SQL thing, by the way, but I’ll demonstrate it on MySQL. I often find this column type in other people’s database schemas, and I wonder if the designer gave it a thought before using it. It’s true, that in the beginning it looks simple
mysql datetime now avoiddatabase scheme howto development linux gmt greenwich meantime universal world
No further bookmarks found.