[freetds] Out-of-the-box "date format" values for "default" and "en_US" locales
shawjef3 at gmail.com
Wed Apr 15 22:24:00 EDT 2015
The use case I have, which is using TDS_FDW to select from SQL Server to
PostgreSQL, forces me to change the colon to a dot, so I support that
On Wed, Apr 15, 2015 at 6:41 PM, Geoff Montee <geoff.montee at gmail.com>
> Hi Matthew,
> On Mon, Apr 13, 2015 at 11:48 PM, <matthew.green at datamartcomputing.com>
> > The vendor (Sybase) default seems to be with a colon (
> > select convert(char(40),getdate(),109);
> > ----------------------------------------
> > Apr 14 2015 8:42:03:660AM
> > Shouldn't we stick to that?
> In the page that you linked, I see that the format style you mention
> is #9 or #109, but I don't see anything to indicate that it is the
> "default." The default style for the convert function in Sybase ASE
> 16.0 appears to use style "100", which omits the milliseconds
> The documentation also says that there should be a dot, not a colon,
> between the seconds and microseconds by default for the "bigdatetime"
> Confusingly, it seems to use a colon by default for the "time" type:
> On another note, FreeTDS's documentation page for locales.conf says this:
> "locales.conf will probably be dropped from FreeTDS one day. Its only
> real purpose now is to control the format of date strings. The Right
> Way™ to deduce the appropriate default date format is from the
> application's locale settings, while allowing an override in
> freetds.conf. That's the direction we're headed."
> Has any thought been given to how date formatting should be handled
> after locales.conf goes away?
> FreeTDS mailing list
> FreeTDS at lists.ibiblio.org
More information about the FreeTDS