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

Groups > comp.databases.mysql > #5358 > unrolled thread

Putting it all together

Back to article view | Back to comp.databases.mysql

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 Luuk <luuk@invalid.lan> - 2014-06-21 13:09 +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 "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-23 05:54 +0000
                    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 Jürgen Exner <jurgenex@hotmail.com> - 2014-06-24 13:41 -0700
                                  Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-24 20:29 -0400
                                  Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-25 08:17 +0200
                                    Re: Storing dates "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-25 06:31 +0000
                                    Re: Storing dates Jürgen Exner <jurgenex@hotmail.com> - 2014-06-25 01:25 -0700
                                    Re: Storing dates Doug Miller <doug_at_milmac_dot_com@example.com> - 2014-06-25 12:02 +0000
                                      Re: Storing dates "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-25 12:17 +0000
                            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 Geoff Muldoon <geoff.muldoon@trap.gmail.com> - 2014-06-25 09:03 +1000
                                  Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-24 20:27 -0400
                                    Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-25 17:15 +0200
                                      Re: Storing dates Jerry Stuckle <jstucklex@attglobal.net> - 2014-06-25 11:43 -0400
                                  Re: Storing dates Geoff Muldoon <geoff.muldoon@trap.gmail.com> - 2014-06-25 11:34 +1000
                                    Re: Storing dates Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-06-25 08:20 +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 "Erick T. Barkhuis" <erick.use-net@ardane.c.o.m> - 2014-06-21 12:27 +0000
                Re: Putting it all together Jürgen Exner <jurgenex@hotmail.com> - 2014-06-21 08:25 -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 5 — ← Prev page 1 2 [3] 4 5  Next page →

#5411 — Re: Storing dates

On Sun, 22 Jun 2014 10:32:09 -0400, Jerry Stuckle wrote:

> On 6/22/2014 10:24 AM, Erick T. Barkhuis wrote:
>> Jerry Stuckle:
>> 
>>> On 6/22/2014 4:03 AM, Erick T. Barkhuis wrote:
>>>> 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.
>>>
>>> Why not, Erick?  It's a good format which sorts naturally.
>> 
>> But apparently, it wants date formats to be three days off!
>> It might sort naturally, but it's not accurate enough.

> No, "9" is September.  The full date is September 12th, 1967.  The
> difference in languages and punctuation is causing confusion.

Yes Jerry, but Arno wrote:

1967-09-12 for the 9. September of 1967

Which is the iso 8601 representation of 12th sep 1967 followed by the 
text representation of 9th sep 1967.

i.e. Arno made a booboo!

-- 
Denis McMahon, denismfmcmahon@gmail.com

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

#5407 — Re: Storing dates

On 22 Jun 2014 14:24:12 GMT, "Erick T. Barkhuis"
<erick.use-net@ardane.c.o.m> wrote in comp.databases.mysql:
>>>> 1967-09-12 for the 9. September of 1967
>
>But apparently, it wants date formats to be three days off!

:-)

Good one!!!

jue

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

#5406 — 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]

#5405 — 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]

#5408 — 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]

#5410 — 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]

#5458 — 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]

#5460 — Re: Storing dates

On Tue, 24 Jun 2014 22:27:24 +0200, Thomas 'PointedEars' Lahn
<PointedEars@web.de> wrote in comp.databases.mysql:

>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.

If this bothers you so much then please filter me. I don't want to be
responsible for you dying of a heart attack.

>> 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.

If this bothers you so much then please filter me. I don't want to be
responsible for you dying of a heart attack.

>>>>>> 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.

If as you are claiming 1967-31-09 is a valid date in ISO-8601, then
please describe verbatim, which date this would be.

>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.

Funny. Here you are arguing that my statement "Then you are not seeing a
valid date in ISO-8601 format." is correct. Now, which one is it?

jue

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

#5463 — Re: Storing dates

On 6/24/2014 4:41 PM, Jürgen Exner wrote:
> On Tue, 24 Jun 2014 22:27:24 +0200, Thomas 'PointedEars' Lahn
> <PointedEars@web.de> wrote in comp.databases.mysql:
> 
>> 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.
> 
> If this bothers you so much then please filter me. I don't want to be
> responsible for you dying of a heart attack.
> 

Jürgen,

Pointed Head is just reverting to his pedantic self.  He does this when
he can't repeat someone's answer (usually a day or two later - he never
comes up with the correct answer on his own) yet feels he has to say
something.

He's well known for his trolling in several newsgroups.

-- 
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
==================

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

#5465 — Re: Storing dates

J�rgen Exner wrote:

> On Tue, 24 Jun 2014 22:27:24 +0200, Thomas 'PointedEars' Lahn
> <PointedEars@web.de> wrote in comp.databases.mysql:
> 
>>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.
> 
> If this bothers you so much then please filter me.

Since you appear to be a luser, or DAU in German, I will probably do that.  
However, that does not change the fact that you are violating standards, and 
thereby cause problems to all other participants.  And that, after all, your 
name is not displayed properly everywhere.  For example, I see U+FFFD 
REPLACEMENT CHARACTER where the umlaut should be.  Other people might see a 
question mark.  And that is just your “From”.  The same problem exists with 
your ”Subject” header fields, should they contain non-ASCII characters.

In addition, by using outdated software you allow security vulnerabilities 
on your system to persist.  This is particularly severe because you use it 
to connect to a server that is on the Internet.  If your system is 
compromised, that will not only affect you, but also all other Internet 
users.

> I don't want to be responsible for you dying of a heart attack.

You have never seen me excited.
 
>>> 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.
> 
> If this bothers you so much then please filter me. I don't want to be
> responsible for you dying of a heart attack.

The issue here is not me; it is you, and the general readability of your 
postings and discussions you participate in.  If you do not want your texts 
to be read, write a diary instead.

>>>>what if you see 1967-31-09?
>>> 
>>> Then you are not seeing a valid date in ISO-8601 format.
>>
>>… that statement is wrong.
> 
> If as you are claiming 1967-31-09 is a valid date in ISO-8601, then
> please describe verbatim, which date this would be.

It was late and I have misread.

-- 
PointedEars

Twitter: @PointedEars2
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

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

#5467 — Re: Storing dates

Thomas 'PointedEars' Lahn:

>J�rgen Exner wrote:
>
>> On Tue, 24 Jun 2014 22:27:24 +0200, Thomas 'PointedEars' Lahn
>> <PointedEars@web.de> wrote in comp.databases.mysql:
>> 
>>>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.
>> 
>> If this bothers you so much then please filter me.
>
>Since you appear to be a luser, or DAU in German, I will probably do
>that. 

Good. That's settled, then.

> ...And that, after all, your name is not displayed properly 
> everywhere.  For example, I see U+FFFD REPLACEMENT CHARACTER where
the
> umlaut should be. 

You guessed right. It should indeed be "ü". 
How is that possible, after such a big mistake by Jürgen?


>In addition, by using outdated software you allow security
>vulnerabilities on your system to persist.

Possibly, yes. But at least, he doesn't allow new vulnerabilities,
introduced by later versions of the software, to reach his machine.


> If your system is compromised, that will not only affect
> you, but also all other Internet users.

The whole World goes down the drain!


Thomas, while it's OK to point out mistakes on Usenet, whenever
necessary, it is very much appreciated if you don't overdo things. Your
never ending repeated complaints about these things aren't really
applauded by the crowd.

-- 
Erick

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

#5468 — Re: Storing dates

On Wed, 25 Jun 2014 08:17:04 +0200, Thomas 'PointedEars' Lahn
<PointedEars@web.de> wrote in comp.databases.mysql:
>
>It was late and I have misread.

Ok, happens to the best of us.
I accept your deeply felt, sincere apology.

jue

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

#5476 — Re: Storing dates

Thomas 'PointedHead' Lahn <PointedEars@web.de> wrote in 
news:1974542.hTQF10sdcN@PointedEars.de:

> J�rgen Exner wrote:
> 
>> On Tue, 24 Jun 2014 22:27:24 +0200, Thomas 'PointedHead' Lahn
>> <PointedEars@web.de> wrote in comp.databases.mysql:
>> 
>>>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.
>> 
>> If this bothers you so much then please filter me.
> 
> Since you appear to be a luser, or DAU in German, I will probably do that.  
> However, that does not change the fact that you are violating standards, and 
> thereby cause problems to all other participants.  

Says the assclown who persists in using non-ASCII characters in his own posts, "thereby 
caus[ing] problems to all other particpants", e.g.

> question mark.  And that is just your “From”.  The same problem exists with 
> your ”Subject” header fields, should they contain non-ASCII characters.

Hypocrite.

<long overdue plonk>

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

#5477 — Re: Storing dates

Doug Miller:

>Thomas 'PointedHead' Lahn <PointedEars@web.de> wrote in 
>news:1974542.hTQF10sdcN@PointedEars.de:
>

>>>>Unencoded non-ASCII characters in message headers are not
>>>>allowed by RFC 5536. 
>
>Says the assclown who persists in using non-ASCII characters in his
>own posts, "thereby caus[ing] problems to all other particpants", e.g.
>
>> question mark.  And that is just your “From”. 

Erm...Thomas mentioned the headers, not the body text.
And he declares:
 Content-Type: text/plain; charset="UTF-8"
for his own posts.
Your XNews appears to be unable to handle that correctly.


Thomas uses extended characters a lot. I would not rule out the
possibility that he likes them, because he knows that plenty of Usenet
denizens are using a news client that can't handle those characters.


-- 
Erick

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

#5412 — 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]

#5413 — 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]

#5409 — 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]

#5414 — 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]

#5421 — 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]

#5424 — 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]

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

Back to top | Article view | comp.databases.mysql

csiph-web