Re: Re: DB_Table: Summary and Pre-Call

Paul: I haven't looked at the class at all, but am following this discussion... On Tue, Apr 06, 2004 at 03:32:35PM -0500, Paul M Jones wrote: > 3. All RDBMS engines store and present date-time info differently, and > have different limits on the range of dates and times they can store. Take a look at http://www.analysisandsolutions.com/code/dates.htm on how to get dates into and out of many DBMS's using the standard SQL-99/ISO format. > (1) It becomes difficult to tell, from structure alone, that a > VARCHAR(19) field is in fact an ISO DATE+TIME field; While there are some circumstances where I've resorted to storing dates as strings,[1] it doesn't seem to be a good idea for general practice. Also, VARCHAR isn't always the best choice, particularly in cases where one is trying to optimize searches on the table -- fixed with column types are better in most DBMS's. --Dan [1]: The situations at hand were ones where the date is used for internal program purposes and never needs to be referenced by the public/other programs. -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409