NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
NLS_CALENDAR: Oracle's $[ ? (Score:1)
My first thought was that I could see this being a problem in exactly the same way as Perl's $[ [perl.org] in other words, setting this in too wide of a scope is going to break a lot of code making certain assumptions.
Actually, that's not quite fair. I can at least see where NLS_CALENDAR would be useful. :)
Re:NLS_CALENDAR: Oracle's $[ ? (Score:2)
Yeah, Oracle has a lot of settings like that, particularly involving dates. Personally, I'm really bugged by the default datemask: DD-Mmm-YYYY (25-Dec-2006). I'm in the US, using a US product, receiving a date that doesn't look like anything I see on a regular basis and which has no useful sorting properties. You can set this parameter at three levels: for the whole server (augh), for each session, and as an explicit parameter each time you set a date. Strangely enough one system I've been on forever has had this mask changed to DD-mmm-YYYY (25-dec-2006), which looks even weirder. But I just leave this setting alone, which reminds me to always explicitly convert my timestamps, so hopefully I will never accidentally code something that breaks when someone else uses it with a different setting.
A related annoyance is that you can't set this parameter for your session with a bind variable [perl.org].
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Reply to This
Parent