Re: tclodbc, SQL Server, date nighmare
- From: Laurent Duperval <lduperval@xxxxxxxxx>
- Date: Fri, 27 Apr 2007 11:48:20 -0400
On Wed, 25 Apr 2007 18:38:35 +0000, Bryan Oakley wrote:
Have you considered trying the following? (caveat, I've never used tclodbc):
set date "'[clock format ...]'"
db "select uuid from extract where savetime < $date"
In other words, put the single quotes inside the variable $date.
Admittedly, this is just a wild guess on my part.
Yes, I have. I had tried other variations of this, but the end result was
the same: it was converted to ''2005-12-12'' instead of '2005-12-12'.
Is there an equivalent to 'to_date()' in SQL Server? Maybe that might
help. I will search to see.
I don't know if I said this before but I also tried snodbc, thinking it
was an issue with tclodbc, but I get the same behaviour.
*Someone* must have done something like this at some point. What was your
secret? :-)
L
.
- Follow-Ups:
- Re: tclodbc, SQL Server, date nighmare
- From: tunity5
- Re: tclodbc, SQL Server, date nighmare
- From: Laurent Duperval
- Re: tclodbc, SQL Server, date nighmare
- References:
- tclodbc, SQL Server, date nighmare
- From: lduperval
- Re: tclodbc, SQL Server, date nighmare
- From: Bryan Oakley
- tclodbc, SQL Server, date nighmare
- Prev by Date: Re: tk_getOpenFile segmentation fault with PDFs
- Next by Date: Re: tclodbc, SQL Server, date nighmare
- Previous by thread: Re: tclodbc, SQL Server, date nighmare
- Next by thread: Re: tclodbc, SQL Server, date nighmare
- Index(es):
Relevant Pages
|