|
From: John H. <jh...@im...> - 2017-06-29 20:47:20
|
On Thu, 29 Jun 2017, Alex Malmyguine wrote:
> Virtually every MS SQL developer would be confused to a high degree by
> this format, as it is virtually never used anywhere in MS SQL Server
> environments. Using JDBC is a tiny niche practice whereas the hugely
> vast majority use nothing but SSMS. Insisting on forcing this format on
> them would not be welcome.
>
> The setting for specifying date/timestamp formats is already in
> Squirrel, all that you might want to do is apply it to the output of the
> generated scripts.
Counterargument: while the {ts} format is unexpected, it *does* work
(assuming the decimal places are limited), and (this is the important bit)
it has the benefit of being robust in the face of different locales' date
formats.
If you're generating locale-specific-formatted date data in SQL, sure it
will work when *you* run that SQL, but relying it to work always for
everyone will eventually come back to bite you.
Yes, I've been badly bitten by this assumption in the past.
So there might need to be a separate date option for generated SQL,
offering localized date formats or {ts} format with specified decimal
places, or a locale-independent common format (e.g. ISO 8601).
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jh...@im... FALaholic #11174 pgpk -a jh...@im...
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
...every time I sit down in front of a Windows machine I feel as
if the computer is just a place for the manufacturers to put their
advertising. -- fwadling on Y! SCOX
-----------------------------------------------------------------------
5 days until the 241st anniversary of the Declaration of Independence
|
