uncleflo
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 1 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile work user process database share manage hardware professional buy industry internet dance advice installation developer 3d camera search material access customer travel test standard review documentation css money engineering engine develop webdesign device photography digital api speed source management program phone discussion question event client story simple water marketing app content yacht setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
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.