WHERE (06/06/1978 < 06/06/1979) returns false ?

Rudy Velthuis wrote:
> Skybuck Flying wrote:
>
>> After 4 weeks I shall remove you from the killfile and see how you do.
>
> LOL! Who cares?
very true

why not ban yourself and make all happy

and then you will not have to put up with abuse from us
as we return what you give

Jim P
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

Skybuck Flying wrote:
> For something as simple as comparing dates: no.
>
> Bye,
> Skybuck.
>
>
but then you would have the answer instead of making us your manual.

Jim P.
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

Skybuck Flying wrote:
> The finally code would have looked something like:
>
> (Birthdate < '06/06/1979')
>
> Since Birthdate is a date field the SQL interpreter could have known the
> string should contain a date.
>
Why?

> Anything else would not make any sense ?!?
>
> Bye,
> Skybuck.
>
>
>
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

Skybuck Flying wrote:
> For something as simple as comparing dates: no.
>
> Bye,
> Skybuck.

You obviously aren't finding it that simple. Using the manual tells you how
to do these things properly in an instant.
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

No need for manuals, others mention it on the internet.

I have never before seen such a weird way of specifieing a date so I tried
out many things to see what would work and what not.

Apperently the other ones don't work and # has to be used for ms access.

However I am switching to mysql so sooner or later I might have to use a
different date string (?)

Bye,
Skybuck.
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

In article ,
says...
> Maybe quotes are needed,
>
> So far this seems to be working:
>
> AND (''06/06/1978'' < ''06/06/1979'')
>
> I'll try using quotes one more time

It's comparing them as strings, not dates. If you put them in the
format yyyy-mm-dd, either one will work.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

In article ,
says...
> Following SQL example works:
>
> (Birthday <> null) AND
> (Birthday > #06/06/1978#) AND
> (Birthday < #06/06/1979#)

The #'s tell me you're working with Access, which is probably the least
standards-compliant database you can find.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

In article ,
says...
> The finally code would have looked something like:
>
> (Birthdate < '06/06/1979')
>
> Since Birthdate is a date field the SQL interpreter could have known the
> string should contain a date.

Or did it think you wanted to convert the date to a string and compare
as strings? It has no way of knowing what you want.

>
> Anything else would not make any sense ?!?

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

Zathras wrote:
> On Sun, 6 Jan 2008 12:35:16 -0000, "Paul Lautman"
> wrote:
>
>> Have you ever considered reading a manual?
>
> Do a search on Usenet and you'll find that is a question often put to
> the infamous Skybuck. He prefers people to do his work for him and
> then calls it collaboration.
>

tell me about it
at least he's not as bad as the mi5 guy......
ish
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ? 

Ummm... just guessing here because I'm a noob to PHP and to a lesser extent,
sort of a noob to MySQL.

I would suspect that your dates aren't being recognized as dates at all, but
rather, as expressions containing some integers and the slashes are being
interpreted as operators - so the larger the right-hand divisor, the smaller
the result will be.

Thus your statement WHERE (06/06/1978 < 06/06/1979) will be false.

With MySQL I think the proper syntax would be 'YYYY-MM-DD' to pass a
literal date as a parameter. With PHP dates seem to be oriented around the
UNIX timestamp and most of the code I've done/seen so far approaches dates
as either the Unix timestamp or as a formatted string generated by coercing
the timestamp or the time() function into printable text.

Again this is just the comments of a noob so your results may vary.

V



"Skybuck Flying" wrote in message

> WHERE (06/06/1978 < 06/06/1979) returns false ?
>
> Clearly 1978 is smaller than 1979 ?
>
> These are dates...
>
> Why is the comparision failing ?
>
> Bye,
> Skybuck.
>
 >> Stay informed about: WHERE (06/06/1978 06/06/1979) returns false ?