Re: Using INTEGER instead of VARCHAR/DATE - is this a way to faster access?

> From: Zbigniew > >> switching from DATE to "more numeric" data type may not be necessary... I would hope that the query optimizer converts '2014-11-02' to the three-bytes internal representation of DATE before doing the query, in which case, DATE should actually be a tiny bit faster than TIM

Re: Using INTEGER instead of VARCHAR/DATE - is this a way to faster access?

2014-10-31 5:29 GMT+01:00, Jan Steinman : > What about using ENUMs? They have nearly the performance of INTEGERs, but > you don't have to maintain a string mapping in your programming logic. So you guys (Jan and "hsv") suggest, that switching from DATE to "more numeric" data type may not be neces