QueryNew() does support 64-bit integers ("BigInt") - how about storing the dates as milliseconds since 1970 or something like that? Would obviously require a couple of conversion functions but would get around your issue here.
Oh, plus I'm a muppet. Use "timestamp" as the data type.
It would be nice if timestamp was listed in the documentation online as an option, then I would have already tried it on my own.
Sure would, looked online and was only date and time. However mess up the syntax and the error message tells you timestamp is an option.
It's in the footnotes.
But, yeah, would be better if Adobe got it right and didn't rely on people to correct their own docs for them. That footnote from Paul has been there for over a year... and I know those posts are moderated by the people who maintain the docs. How lazy is it to not correct them even when someone's taken the time to point the correction out to them!
That'll teach me to not check all versions of the documentation and scroll down to the bottom of each one to find ALL the possible options of any tag and|or function.
Sheesh silly me.
I started with the CF8 version of the function documentation because that often comes up first in Google searches for just a tag or function name.
Heh. And "g'day Ian", btw. You don't seem to have been around here much recently?
I have this URL bookmarked:
And I browse to it and stick whatever I want at the end of it. That way I stick to the CF9 docs. I find the CF9 docs site quite a lot quicker than the CF8 ones. That and it's more relevant to me (as we've finally migrated to CF9).
It does seem odd (and annoying) that the old CF8 docs have been indexed by Google better than the CF9 docs have been.
I don't get the Adobe forum emails to my day-in-day-out email address anymore.
So unless I have a reason and|or enough boredome to come to the website to seek help or those that need help, I don't get around here very often these days.