Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #13930 > unrolled thread

Putting it all together

Back to article view | Back to comp.lang.php

Contents

  Putting it all together richard <noreply@example.com> - 2014-06-20 10:20 -0400
    Re: Putting it all together Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-20 08:11 -0700
      Re: Putting it all together richard <noreply@example.com> - 2014-06-20 11:24 -0400
        Re: Putting it all together Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-20 17:15 +0000
        Re: Putting it all together Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-20 20:01 -0700
    Re: Putting it all together Jürgen Exner <jurgenex@hotmail.com> - 2014-06-20 08:21 -0700
    Re: Putting it all together Norman Peelman <npeelman@cfl.rr.com> - 2014-06-20 21:06 -0400
    Re: Putting it all together Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-21 03:02 +0000
    Re: Putting it all together Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-21 03:09 +0000
    Re: Putting it all together Jürgen Exner <jurgenex@hotmail.com> - 2014-06-20 20:13 -0700
      Re: Putting it all together richard <noreply@example.com> - 2014-06-20 23:34 -0400
        Re: Putting it all together Jürgen Exner <jurgenex@hotmail.com> - 2014-06-20 20:48 -0700
        Re: Putting it all together Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-20 21:00 -0700
        Re: Putting it all together Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-21 04:22 +0000
          Re: Putting it all together Jürgen Exner <jurgenex@hotmail.com> - 2014-06-20 22:11 -0700
            Re: Putting it all together Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-20 22:39 -0700
          Re: Putting it all together gordonb.zp2md@burditt.org (Gordon Burditt) - 2014-06-21 04:15 -0500
            Storing dates (was: Putting it all together) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-21 12:15 +0200
              Re: Storing dates richard <noreply@example.com> - 2014-06-21 11:10 -0400
                Re: Storing dates Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-21 17:42 +0000
                  Re: Storing dates richard <noreply@example.com> - 2014-06-21 14:28 -0400
                    Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-21 12:04 -0700
                    Re: Storing dates Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-21 19:06 +0000
                      Re: Storing dates Tim Streater <timstreater@greenbee.net> - 2014-06-21 22:06 +0100
                        Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-21 17:09 -0400
                          Re: Storing dates Tim Streater <timstreater@greenbee.net> - 2014-06-21 22:33 +0100
                            Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-21 17:49 -0400
                            Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-22 14:38 +0200
                        Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-21 14:31 -0700
                          Re: Storing dates Tim Streater <timstreater@greenbee.net> - 2014-06-21 22:44 +0100
                          Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-22 14:59 +0200
                    Re: Storing dates Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-21 23:19 +0000
                    Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-22 08:53 +0200
                      Re: Storing dates "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-22 08:03 +0000
                        Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-22 09:29 -0400
                          Re: Storing dates "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-22 14:24 +0000
                            Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-22 10:32 -0400
                              Re: Storing dates "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-22 14:45 +0000
                              Re: Storing dates Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-22 19:44 +0000
                            Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-22 08:26 -0700
                          Re: Storing dates gordonb.q26od@burditt.org (Gordon Burditt) - 2014-06-22 10:00 -0500
                        Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-22 16:47 +0200
                          Re: Storing dates richard <noreply@example.com> - 2014-06-22 13:55 -0400
                            Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-22 12:31 -0700
                              Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-24 22:27 +0200
                            Re: Storing dates Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-22 19:52 +0000
                            Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-22 21:52 +0200
                      Re: Storing dates richard <noreply@example.com> - 2014-06-22 14:05 -0400
                        Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-22 21:56 +0200
                          Re: Storing dates richard <noreply@example.com> - 2014-06-22 22:46 -0400
                            Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-23 08:11 +0200
                              Re: Storing dates richard <noreply@example.com> - 2014-06-23 02:37 -0400
                                Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-23 11:10 +0200
                                Re: Storing dates Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-23 06:50 -0700
                                  Re: Storing dates richard <noreply@example.com> - 2014-06-23 11:13 -0400
                                    Re: Storing dates Evan Platt <evan@theobvious.espphotography.com.invalid> - 2014-06-23 09:13 -0700
                                      Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-23 22:33 +0200
                          Re: Storing dates richard <noreply@example.com> - 2014-06-22 23:04 -0400
                            Re: Storing dates Arno Welzel <usenet@arnowelzel.de> - 2014-06-23 08:12 +0200
                              Re: Storing dates Geoff Muldoon <geoff.muldoon@trap.gmail.com> - 2014-06-23 16:45 +1000
                                Re: Storing dates richard <noreply@example.com> - 2014-06-23 07:58 -0400
                                  Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-23 09:50 -0700
                                    Re: Storing dates Christoph Michael Becker <cmbecker69@arcor.de> - 2014-06-23 19:02 +0200
                                  Re: Storing dates Geoff Muldoon <geoff.muldoon@trap.gmail.com> - 2014-06-24 12:00 +1000
                                Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-24 22:38 +0200
                        Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-22 15:30 -0700
                          Re: Storing dates "Peter H. Coffin" <hellsop@ninehells.com> - 2014-06-22 20:10 -0500
            Re: Putting it all together Jürgen Exner <jurgenex@hotmail.com> - 2014-06-21 03:34 -0700
        Re: Putting it all together Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-21 10:23 +0000
        Re: Putting it all together bill <william@TechServSys.com> - 2014-06-21 07:03 -0400
          Re: Putting it all together Denis McMahon <denismfmcmahon@gmail.com> - 2014-06-21 15:11 +0000
        Re: Putting it all together "Peter H. Coffin" <hellsop@ninehells.com> - 2014-06-21 10:57 -0500
        Re: Putting it all together Arno Welzel <usenet@arnowelzel.de> - 2014-06-22 08:45 +0200

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

#13991 — Re: Storing dates

>>> 1967-09-12 for the 9. September of 1967
>>> BTW: This is why ISO 8601 had been invented 

>> If that's the case, I don't like ISO 8601.
 
> Why not, Erick?  It's a good format which sorts naturally.

Read the numbers very, very carefully.
 

[toc] | [prev] | [next] | [standalone]

#13990 — Re: Storing dates

Erick T. Barkhuis, 2014-06-22 10:03:

> Arno Welzel:
> 
>> 1967-09-12 for the 9. September of 1967
>> BTW: This is why ISO 8601 had been invented 
> 
> If that's the case, I don't like ISO 8601.

Of course it was just a typo and 1967-09-12 is for 12. September of 1967 ;-)


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#13993 — Re: Storing dates

On Sun, 22 Jun 2014 16:47:36 +0200, Arno Welzel wrote:

> Erick T. Barkhuis, 2014-06-22 10:03:
> 
>> Arno Welzel:
>> 
>>> 1967-09-12 for the 9. September of 1967
>>> BTW: This is why ISO 8601 had been invented 
>> 
>> If that's the case, I don't like ISO 8601.
> 
> Of course it was just a typo and 1967-09-12 is for 12. September of 1967 ;-)

But how are us humans supposed to know which comes first?
what if you see 1967-31-09?
if it read 1967-Sep-09 then there is no guessing is there?

[toc] | [prev] | [next] | [standalone]

#13995 — Re: Storing dates

On Sun, 22 Jun 2014 13:55:49 -0400, richard <noreply@example.com> wrote
in comp.databases.mysql:
>>>> BTW: This is why ISO 8601 had been invented 
>> Of course it was just a typo and 1967-09-12 is for 12. September of 1967 ;-)
>
>But how are us humans supposed to know which comes first?

Simple: because it is unambiguously defined in ISO 8601.

>what if you see 1967-31-09?

Then you are not seeing a valid date in ISO-8601 format. 

>if it read 1967-Sep-09 then there is no guessing is there?

Yes there is, because in many languages "Sep" doesn't make any sense.
Furthermore obviously dates in that format cannot be sorted easily.

jue

[toc] | [prev] | [next] | [standalone]

#14037 — Re: Storing dates

J�rgen Exner wrote:
^^^^^^^^^^^^
Unencoded non-ASCII characters in message headers are not allowed by
RFC 5536.  Please fix your newsreader or switch to a working one.

> On Sun, 22 Jun 2014 13:55:49 -0400, richard <noreply@example.com> wrote
> in comp.databases.mysql:

It's attribution *line*, _not_ attribution novel.  Please adjust/fix your 
newsreader or switch to one that allows you to not make life harder for your 
readers.

>>>>> BTW: This is why ISO 8601 had been invented
>>> Of course it was just a typo and 1967-09-12 is for 12. September of 1967
>>> ;-)
>>
>>But how are us humans supposed to know which comes first?
> 
> Simple: because it is unambiguously defined in ISO 8601.
                        ^^^^^^^^^^^^^
Which is why …
 
>>what if you see 1967-31-09?
> 
> Then you are not seeing a valid date in ISO-8601 format.

… that statement is wrong.

The ISO 8601 date format is unambiguously defined because it always has the 
year number (Y), followed by the month number (M), optionally followed by 
the day-of-month number (D): YYYY-MM-DD or YYYYMMDD.  Whereas YYYY, YYYY-MM, 
YY-MM-DD, and YYMMDD had been allowed, but the latter two were recommended 
against and have been abolished in 2004 CE.

There is no YYYY-DD-MM format specified there, and since there are only 12 
months in the Gregorian calendar, there cannot be a 31st.

<https://en.wikipedia.org/wiki/ISO_8601#Calendar_dates>

F'up2 comp.lang.mysql
 
-- 
When all you know is jQuery, every problem looks $(olvable).

[toc] | [prev] | [next] | [standalone]

#13997 — Re: Storing dates

On Sun, 22 Jun 2014 13:55:49 -0400, richard wrote:

> On Sun, 22 Jun 2014 16:47:36 +0200, Arno Welzel wrote:
> 
>> Erick T. Barkhuis, 2014-06-22 10:03:
>> 
>>> Arno Welzel:
>>> 
>>>> 1967-09-12 for the 9. September of 1967 BTW: This is why ISO 8601 had
>>>> been invented
>>> 
>>> If that's the case, I don't like ISO 8601.
>> 
>> Of course it was just a typo and 1967-09-12 is for 12. September of
>> 1967 ;-)
> 
> But how are us humans supposed to know which comes first? what if you
> see 1967-31-09?

If you know it's an iso 8601 date then you know that the first 4 digits 
(1967) are the year, the next 2 digits (31) are the month and the last 2 
digits (09) are the day number.

> if it read 1967-Sep-09 then there is no guessing is there?

1967-sep-09 is not an iso 8601 date.

Iso 8601 defines a date as:

[4 digit Year Number][-][2 digit Month Number][-][2 digit Day Number]

So if "1967-31-09" was valid in iso 8601 it would actually be 
"1969-07-09" or the 9th of July 1969, because July 1969 is the 31st month 
starting at January 1967.

The reason iso 8601 is good is that in the string form, iso 8601 dates 
sort properly, ie ascending / descending string order is also ascending / 
descending date order. If you don't understand this, you obviously don't 
understand anything about string sorting either.

Oh right. You don't.

-- 
Denis McMahon, denismfmcmahon@gmail.com

[toc] | [prev] | [next] | [standalone]

#13998 — Re: Storing dates

richard, 2014-06-22 19:55:

> On Sun, 22 Jun 2014 16:47:36 +0200, Arno Welzel wrote:
> 
>> Erick T. Barkhuis, 2014-06-22 10:03:
>>
>>> Arno Welzel:
>>>
>>>> 1967-09-12 for the 9. September of 1967
>>>> BTW: This is why ISO 8601 had been invented 
>>>
>>> If that's the case, I don't like ISO 8601.
>>
>> Of course it was just a typo and 1967-09-12 is for 12. September of 1967 ;-)
> 
> But how are us humans supposed to know which comes first?

They look what ISO 8601 defines.

> what if you see 1967-31-09?

This is an invalid date according to ISO 8601.

> if it read 1967-Sep-09 then there is no guessing is there?

This is also an invalid date according to ISO 8601.


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#13994 — Re: Storing dates

On Sun, 22 Jun 2014 08:53:17 +0200, Arno Welzel wrote:

> richard, 2014-06-21 20:28:
> 
>> On Sat, 21 Jun 2014 17:42:29 +0000 (UTC), Doug Miller wrote:
>> 
>>> richard <noreply@example.com> wrote in news:1mddkhwt2mr0v$.1m6eithcu7iod.dlg@
>>> 40tude.net:
>>>
>>>> As for the date usage on MY database tables, I am only using a date as a
>>>> reference.
>>>
>>> Patently false, as you have posted questions here asking for help resolving your problems in 
>>> sorting by the date.
>>>
>>>> I really don't give a damn what your philosophy or ideals are
>>>> behind the so called "proper ways" of obtaining a date.
>>>  
>>> Which is exactly *why* you have problems sorting by the date.
>> 
>> The problem with sorting is, it treats any value given as a string, then
>> determines which has the lowest value in total.
>> 1
>> 2
>> 3
>> 10
>> 20
>> 30
>> 100
>> 200
>> 300
> 
> That's why *thinking* about how to store information is important.
> 
> Even if you don't like to use a date datatype you should store the date
> values in a way that they can be used for sorting - so year first, then
> month, then day and all with leading zeros:
> 
> 2014-06-22 for the 22. June of 2014
> 1967-09-12 for the 9. September of 1967
> 
> and so on.
> 
> BTW: This is why ISO 8601 had been invented - see
> <http://en.wikipedia.org/wiki/ISO_8601>.

Doesn't matter anymore. I am using the numeric day system instead.
where $date=date(z).

[toc] | [prev] | [next] | [standalone]

#13999 — Re: Storing dates

richard, 2014-06-22 20:05:

> On Sun, 22 Jun 2014 08:53:17 +0200, Arno Welzel wrote:
> 
[about date storage in databases]
>> BTW: This is why ISO 8601 had been invented - see
>> <http://en.wikipedia.org/wiki/ISO_8601>.
> 
> Doesn't matter anymore. I am using the numeric day system instead.
> where $date=date(z).

Really? Literally "where $date=date(z)"? Looks very unusual.

And even if this would make any sense - it least in MySQL date() is
*not* a "numeric day system":

<http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_date>

Or did you switch to another database system?


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#14004 — Re: Storing dates

On Sun, 22 Jun 2014 21:56:57 +0200, Arno Welzel wrote:

> richard, 2014-06-22 20:05:
> 
>> On Sun, 22 Jun 2014 08:53:17 +0200, Arno Welzel wrote:
>> 
> [about date storage in databases]
>>> BTW: This is why ISO 8601 had been invented - see
>>> <http://en.wikipedia.org/wiki/ISO_8601>.
>> 
>> Doesn't matter anymore. I am using the numeric day system instead.
>> where $date=date(z).
> 
> Really? Literally "where $date=date(z)"? Looks very unusual.
> 
> And even if this would make any sense - it least in MySQL date() is
> *not* a "numeric day system":
> 
> <http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_date>
> 
> Or did you switch to another database system?

http://www.php.net//manual/en/function.date.php

Day 	--- 	---
d 	Day of the month, 2 digits with leading zeros 	01 to 31
D 	A textual representation of a day, three letters 	Mon through Sun
j 	Day of the month without leading zeros 	1 to 31
l (lowercase 'L') 	A full textual representation of the day of the week 	
Sunday through Saturday
N 	ISO-8601 numeric representation of the day of the week (added in PHP
5.1.0) 	1 (for Monday) through 7 (for Sunday)
S 	English ordinal suffix for the day of the month, 2 characters 	st, nd,
rd or th. Works well with j
w 	Numeric representation of the day of the week 	0 (for Sunday) through 6
(for Saturday)
z 	The day of the year (starting from 0) 	0 through 365

http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_dayofyear

dayofyear() can now be used to convert back to calendar format.

[toc] | [prev] | [next] | [standalone]

#14006 — Re: Storing dates

richard, 2014-06-23 04:46:

> On Sun, 22 Jun 2014 21:56:57 +0200, Arno Welzel wrote:
> 
>> richard, 2014-06-22 20:05:
>>
>>> On Sun, 22 Jun 2014 08:53:17 +0200, Arno Welzel wrote:
>>>
>> [about date storage in databases]
>>>> BTW: This is why ISO 8601 had been invented - see
>>>> <http://en.wikipedia.org/wiki/ISO_8601>.
>>>
>>> Doesn't matter anymore. I am using the numeric day system instead.
>>> where $date=date(z).
>>
>> Really? Literally "where $date=date(z)"? Looks very unusual.
>>
>> And even if this would make any sense - it least in MySQL date() is
>> *not* a "numeric day system":
>>
>> <http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_date>

This does still not explain, why you use "where $date=date(z)". PHP
itself does not execute SQL statements.



-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#14009 — Re: Storing dates

On Mon, 23 Jun 2014 08:11:46 +0200, Arno Welzel wrote:

> richard, 2014-06-23 04:46:
> 
>> On Sun, 22 Jun 2014 21:56:57 +0200, Arno Welzel wrote:
>> 
>>> richard, 2014-06-22 20:05:
>>>
>>>> On Sun, 22 Jun 2014 08:53:17 +0200, Arno Welzel wrote:
>>>>
>>> [about date storage in databases]
>>>>> BTW: This is why ISO 8601 had been invented - see
>>>>> <http://en.wikipedia.org/wiki/ISO_8601>.
>>>>
>>>> Doesn't matter anymore. I am using the numeric day system instead.
>>>> where $date=date(z).
>>>
>>> Really? Literally "where $date=date(z)"? Looks very unusual.
>>>
>>> And even if this would make any sense - it least in MySQL date() is
>>> *not* a "numeric day system":
>>>
>>> <http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_date>
> 
> This does still not explain, why you use "where $date=date(z)". PHP
> itself does not execute SQL statements.

Look dunbshit, I am not using "where" here as an sql statement or property.

for instance you see something like mm-dd-yy then the writer says, "Where
m=month, d=day, and y=year".
"Where" is used routinely to define what the writer meant by his
abbreviations and such.

No Mr. Miller, I am not apologizing to him or you.
He's just being an irritating troll now.

[toc] | [prev] | [next] | [standalone]

#14011 — Re: Storing dates

Am 2014-06-23 08:37, schrieb richard:

> Look dunbshit, [...]

Ok, welcome to my filter. My apologies that I did not ignore you earlier.


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#14014 — Re: Storing dates

On Mon, 23 Jun 2014 02:37:14 -0400, richard <noreply@example.com>
wrote:

>Look dunbshit, I am not using "where" here as an sql statement or property.

Wow, I hope Lew reconsiders his offer to help bullis now. 

bullis, you better learn SQL and PHP REAL quick, because you're
alienating the entire group here.
-- 
To reply via e-mail, remove The Obvious and .invalid from my e-mail address.

[toc] | [prev] | [next] | [standalone]

#14016 — Re: Storing dates

On Mon, 23 Jun 2014 06:50:43 -0700, Evan Platt wrote:

> On Mon, 23 Jun 2014 02:37:14 -0400, richard <noreply@example.com>
> wrote:
> 
>>Look dunbshit, I am not using "where" here as an sql statement or property.
> 
> Wow, I hope Lew reconsiders his offer to help bullis now. 
> 
> bullis, you better learn SQL and PHP REAL quick, because you're
> alienating the entire group here.

You certainly have helped on that.
Just because SQL or other lamguages use a common every day word in its
structure does not mean that is the only way that word can be used.
Arno took the context and wrongfully assumed that I was referring to the
use of "where" in the select statement.This is not what I was using the
word for.
And all you do is add agitation to it all purely for wanting to make things
worse than they are.

[toc] | [prev] | [next] | [standalone]

#14018 — Re: Storing dates

On Mon, 23 Jun 2014 11:13:23 -0400, richard <noreply@example.com>
wrote:

>> bullis, you better learn SQL and PHP REAL quick, because you're
>> alienating the entire group here.
>
>You certainly have helped on that.

Take responsibility for your actions, bullis. You calling the regulars
here dumbshits, creating sock puppets when people refuse to help you,
and insulting everyone here means you are 100% responsible for
alienating people here.

>Just because SQL or other lamguages use a common every day word in its
>structure does not mean that is the only way that word can be used.
>Arno took the context and wrongfully assumed that I was referring to the
>use of "where" in the select statement.This is not what I was using the
>word for.

Oh. I misunderstood. In that case, you were fully justified in calling
Arno a dumbshit. </sarcasm>

>And all you do is add agitation to it all purely for wanting to make things
>worse than they are.

See my first paragraph. You can only blame yourself.
-- 
To reply via e-mail, remove The Obvious and .invalid from my e-mail address.

[toc] | [prev] | [next] | [standalone]

#14021 — Re: Storing dates

Evan Platt, 2014-06-23 18:13:

> On Mon, 23 Jun 2014 11:13:23 -0400, richard <noreply@example.com>
> wrote:
> 
>>> bullis, you better learn SQL and PHP REAL quick, because you're
>>> alienating the entire group here.
>>
>> You certainly have helped on that.
> 
> Take responsibility for your actions, bullis. You calling the regulars
> here dumbshits, creating sock puppets when people refuse to help you,
> and insulting everyone here means you are 100% responsible for
> alienating people here.

The best way to deal with such people is to ignore them and not to
produce more off-topic noise.

Thank you!


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#14005 — Re: Storing dates

On Sun, 22 Jun 2014 21:56:57 +0200, Arno Welzel wrote:

> richard, 2014-06-22 20:05:
> 
>> On Sun, 22 Jun 2014 08:53:17 +0200, Arno Welzel wrote:
>> 
> [about date storage in databases]
>>> BTW: This is why ISO 8601 had been invented - see
>>> <http://en.wikipedia.org/wiki/ISO_8601>.
>> 
>> Doesn't matter anymore. I am using the numeric day system instead.
>> where $date=date(z).
> 
> Really? Literally "where $date=date(z)"? Looks very unusual.
> 
> And even if this would make any sense - it least in MySQL date() is
> *not* a "numeric day system":
> 
> <http://dev.mysql.com/doc/refman/5.5/en/date-and-time-functions.html#function_date>
> 
> Or did you switch to another database system?

BTW, date() itself is not anything but a function.
date(z) takes the current date of the server and trasnform it into a number
in the range of 1 to 366.

If the date were 2014-01-01, date(z) would return 1.
Dayofyear() takes that number and transform it back to the calendar date.

In my use of "where", I meant that as "an example", not as used by mysql
select from where stuff.

[toc] | [prev] | [next] | [standalone]

#14007 — Re: Storing dates

richard, 2014-06-23 05:04:

[...]
> BTW, date() itself is not anything but a function.
> date(z) takes the current date of the server and trasnform it into a number
> in the range of 1 to 366.
> 
> If the date were 2014-01-01, date(z) would return 1.
> Dayofyear() takes that number and transform it back to the calendar date.

Yep - but only for the current year. Next year 1 would meen 2015-01-01
and so on.



-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

[toc] | [prev] | [next] | [standalone]

#14010 — Re: Storing dates

In article <53A7C563.6050901@arnowelzel.de>, usenet@arnowelzel.de 
says...
> 
> richard, 2014-06-23 05:04:
> 
> [...]
> > BTW, date() itself is not anything but a function.
> > date(z) takes the current date of the server and trasnform it into a number
> > in the range of 1 to 366.
> > 
> > If the date were 2014-01-01, date(z) would return 1.
> > Dayofyear() takes that number and transform it back to the calendar date.
> 
> Yep - but only for the current year. Next year 1 would meen 2015-01-01
> and so on.

Doesn't the MySQL DATEOFYEAR() function actually take a DATE data type 
input and return a number (in range 1-366)?

Unless of course Richard is talking about some weird non-mysql PHP 
function he has cobbled together.

GM

[toc] | [prev] | [next] | [standalone]

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

Back to top | Article view | comp.lang.php

csiph-web