3 ms·
One of oracle quirks for me is varchar2. What happened to varchar1? Nobody knows.
by vbezhenar 5y ago
One of oracle quirks for me is varchar2. What happened to varchar1? Nobody knows.
- tgv 5y agoTIMESTAMP WITH LOCAL TIMEZONE. Never again.
- beamatronic 5y agoLet me guess, did you get hit with more than one 3:00am?
- tmd83 5y agoLet's not forget that Oracle DB uses the system timezone as the datatype storage (not sure what other database do to be honest) so unless you were running your DB machine as UTC by default their timestamp storage would be ambiguous for DST shift and that's their default. Why wouldn't they store everything in UTC and use the system timezone for parse/formatting I have no clue.
- deleted 5y ago[deleted]
- tracker1 5y agoI've been pushing to run ALL servers as UTC for a few decades now... always store/transmit date+time as UTC as well. If it's mapped to a locale, pair it with that locale... let the client translate to/from local.
- SketchySeaBeast 5y agoOh sorry, are you looking to insert 4001 characters in your varchar2? Buckle up kids, things are gonna get rough.
- kubanczyk 5y agoOr maybe 3999 chars, of which a couple are two-byte. More fun.
- gvenzl 5y agoOracle supports up to 32k VARCHARs since 12.1 released back in 2013. It just needs to be enabled: https://docs.oracle.com/database/121/REFRN/GUID-D424D23B-0933-425F-BC69-9C0E6724693C.htm https://docs.oracle.com/database/121/REFRN/GUID-D424D23B-093...
- icedchai 5y agovarchar1 was varchar. I should say "is", since varchar is still supported, they just recommend varchar2 since varchar "might change" (probably not...)
- marcosdumay 5y agoThat one actually changed already. If you follow the new recommendations, varchar is as good as varchar2.
- icedchai 5y agoGood to know! I haven't had to touch an Oracle database in almost 15 years, but one never knows.