....agreed, but they could start with some common ones
> The problem with that is that the list of database engines is huge, and if
> they decide to "enhance" the system it makes a mockery of this idea
>
> I think the main way of dealing with this is that you should use # for
> Access and ' for SQL Server and (I think) Oracle... no idea about mySQL...
> and format the date in a non-ambiguous format (d mmm yyyy or mmm d yyyy
> works wonders for this)
>
> Philip Arnold
> Director
> Certified ColdFusion Developer
> ASP Multimedia Limited
> T: +44 (0)20 8680 1133
> Date: Sun, 11 Mar 2001 22:48:41 -0000
> From: "Philip Arnold - ASP" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: RE: Dates in OLEDB
> Message-ID: <[EMAIL PROTECTED]>
>
> > This works. Thanks, what a pain!
> >
> > This immediately makes a migration to OLEDB a waste of time. (Might
> > look at it for future apps)
> >
> > It also makes me think there should be a set of new functions in CF:
> >
> > createDBdate(mydate,"theDB")
> > createDBdatetime(mydatetime,"theDB")
> >
> > Where theDB could be "Access", "SQLServer","ODBC"(!) etc.
--
Regards;
Richard Meredith-Hardy
-------------------------------------------------------------
[EMAIL PROTECTED]
Tel: + 44 (0)1462 834776 FAX: + 44 (0)1462 732668
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
