Comments for Stephen J. Houston

Comment on SQL is English by elonelung

elonelung — Fri, 27 Feb 2009 12:24:00 +0000

Dude … take a chillax pill ! …what client are you using … use toad (if you can get a license) … SQL PLUS is fine for me running in the commands using the semi-colon …
no probs …
you have created a table with the table with a column name called ‘date’ … date being a oracle keyword, the database decides to poop itself … ORA-00928s?

SQL> create table TABLE1 (mydate date, myusername varchar2(20));

SQL> INSERT INTO TABLE1(mydate, myusername)
VALUES (’10-jan-2008′, ‘fred’);

blam … no probs … or as the kids would say … brappp brappp brappp

Default string format for date fields is DD-MON-YY
you can use the to_date and to_char functions, which provide support for this ISO-8001 one thing :

select to_char(sysdate,’YYYY-MM-DD’) from dual;

Oracle stores its date data in a special format, and returns data through the to_char function, defaulting the format of the string returned to DD-MON-YYYY …
http://infolab.stanford.edu/~ullman/fcdb/oracle/or-time.html

Also askTom ftw..

Comment on SQL is English by John Girvin

John Girvin — Fri, 27 Feb 2009 12:11:05 +0000

“The great thing about standards is that there are so many to choose from”.

Our product supports multiple database engines out of the box and we hit incompatibilities all the time. We tackle it partially by defining our schema in XML then using XSLT in the build/install process to create engine specific scripts. Some parts we can’t or don’t automate this way though, and those still have to be hand tuned for each engine … I had to navigate the Oracle date formatting maze myself not so long ago.

Comment on Cybersource on Simplifying ePayments by Books and Magazines Blog » Archive » Cybersource on Simplifying ePayments

Fri, 10 Oct 2008 00:09:59 +0000

[...] Original post by Stephen J. Houston [...]