|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:30 AM
Points: 861,
Visits: 1,436
|
|
Such an easy question that feels refreshing and points out an excellent feature for international dates.
Thank you, Steve, Hugo and Mark for the additional explanations and opinions.
Best regards,
Best regards,
Andre Guerreiro Neto
Database Analyst http://www.softplan.com.br MCITPx1/MCTSx2
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, January 24, 2013 9:59 PM
Points: 1,354,
Visits: 1,299
|
|
Call me old fashioned but I would use two columns for this too. The big reason is that I like using portable SQL code and this is new to SQL Server 2008. If I put my code on another company's server and they are using 2005, then it will stop functioning. Why should I subject myself to emergency repairs if I can fix the problem during design time?
I also like writing SQL code that is compatible with Oracle and MySQL. Many of the datetime functions make this difficult but at least I try my best to keep it standardized by using as much ANSI SQL as possible.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Today @ 4:29 AM
Points: 3,226,
Visits: 64,062
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: 2 days ago @ 11:46 AM
Points: 3,448,
Visits: 2,522
|
|
I am surprised that only 62 percents of respondents got this one right.
Thanks, Steve!
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, January 24, 2013 9:59 PM
Points: 1,354,
Visits: 1,299
|
|
mtassin (1/10/2012) Oracle supports storing timezone with dates.
http://docs.oracle.com/cd/B14117_01/server.101/b10759/functions179.htm
Using the portability defense really isn't a good idea... each DB server is different enough, that queries that can run on all of them, likely run poorly on all of them.
I cannot disagree with this. However, would you rather write 3 or 4 versions of a program or just one? I sell a service and the companies I sell it to have a variety of server implementations.
It might be okay to write 3 versions of the same application but then it becomes a problem with enhancements. You need to enhance all of them at the same time and that triples your workload.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:53 AM
Points: 1,176,
Visits: 778
|
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Today @ 4:24 AM
Points: 563,
Visits: 58,824
|
|
| Nice easy question after a day full of issue, bugs and headaches. Thanks.
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Yesterday @ 6:38 PM
Points: 7,077,
Visits: 7,116
|
|
SQLRNNR (1/9/2012) EZ PZ +1
Tom Que conclure à la fin de tous mes longs propos? C'est que les préjugés sont la raison des sots. (Voltaire, 1756)
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 10:57 AM
Points: 1,632,
Visits: 10,850
|
|
A timely question. We're starting to have to deal with lots of time related data coming in from multiple time zones and need to come up with a good strategy for storing/comparing/managing it all. This data type will likely fill the bill for us, so this question is a good start on my research and design. Thanks!
Rob Schripsema Accelitec, Inc
|
|
|
|
|
SSC-Dedicated
           
Group: Administrators
Last Login: 2 days ago @ 1:47 PM
Points: 31,406,
Visits: 13,722
|
|
cengland0 (1/10/2012)
mtassin (1/10/2012) Oracle supports storing timezone with dates.
http://docs.oracle.com/cd/B14117_01/server.101/b10759/functions179.htm
Using the portability defense really isn't a good idea... each DB server is different enough, that queries that can run on all of them, likely run poorly on all of them.
I cannot disagree with this. However, would you rather write 3 or 4 versions of a program or just one? I sell a service and the companies I sell it to have a variety of server implementations.
If you are a software writer that has multiple targets, I can see your point. However the vast majority of us, 90+% of the developers out there write for applications that are not sold, are internal, and target one platform.
Your comment is valid, but you should qualify it with the note that your job requires this. I have almost never seen anyone port code from one RDBMS to another, outside of an ISV. Even when we've switched platforms, it was a data move, not a code move.
For ISVs, hire more people. Don't write queries that suck on all platforms. Rewrite them for different platforms.
Follow me on Twitter: @way0utwest
 Forum Etiquette: How to post data/code on a forum to get the best help
|
|
|
|