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

Groups > comp.lang.php > #1764

Re: problem saving date fields

Show all headers | View raw

On 5/22/2011 12:28 AM, Jeff North wrote:
> On Sat, 21 May 2011 20:01:17 -0400, in comp.lang.php Jerry Stuckle
> <jstucklex@attglobal.net>
> <ir9jom$663$1@dont-email.me>  wrote:
>
>> | On 5/21/2011 12:08 PM, Jeff North wrote:
>> |>  On Sat, 21 May 2011 10:32:20 -0400, in comp.lang.php Jerry Stuckle
>> |>  <jstucklex@attglobal.net>
>> |>  <ir8idn$ojm$1@dont-email.me>   wrote:
>> |>
>
> [snip]
>
>> |>  There is no need to have variables in the code that aren't being used.
>> |
>> | Yes, there is.  In fact, it is quite common to have variables in the
>> | code which are not being use *at this time*.  And very good reasons for
>> | *not* initializing them - as a *programmer* would know.
>
> Programmers who know more that just PHP know that you are full of
> crap.
>

I've probably forgotten more languages than you ever learned - starting 
with autocoder.

> [snip]
>
>> |>>  |>   The SQL statement should be ok - it's the "When I change of them the
>> |>>  |>   other one gets set back to default: 00-00-0000" I'm considering.
>> |>>  |
>> |>>  | The SQL statement is NOT ok.  As he would find if he printed it out as
>> |>>  | was suggested.
>> |>
>> |>  If the SQL statement was not ok then the record wouldn't be updated.
>> |
>> | Or the row (tables have ROWS, not RECORDS) is not being updated with the
>> | correct data - which is the case here.  But then a *programmer* would
>> | understand that.
>
> A row, or record, would NOT be updated if the SQL statement is NOT ok
> - even a moron like you can understand that - oh you do that is why
> you chose to answer the question the way you did.
>

What an idiot.  An incorrect SQL statement can cause the row to be 
inserted or updated with incorrect data also, as is the case here.

However, it takes intelligence to understand that, which you obviously 
do not have.

>> |>>  |>>   | BTW - your sig separator is broken.  It needs to be exactly
>> |>>  |>>   | hyphen-hyphen-space-newline.
>
> [snip]
>
>> |>>  | It has nothing to do with Thunderbird.  It has EVERYTHING to do with
>> |>>  | following usenet standards, in this case RFC 3736.
>> |>
>> |>  Please highlight the line(s) from RFC 3736 that can back up your
>> |>  claim.
>> |>
>> |>>  | But I see you're as clueless about rfcs as you are programming.
>> |>  -- -------------------------------------------------
>> |>  The supplied code is for guideline purposes only.
>> |
>> | Typo - the rfc is 3676,
>
> 3676 and 3736 is NOT a typo not matter how you try to spin it. If you
> are going to speak with the voice of authority then get your facts
> correct first.
>

OK, now we know you are a troll and an anal orifice.

>> | which you could find if you knew how to do a
>> | simple google search.
>
> Everyone would know that they needed to search for "The Text/Plain
> Format and DelSp Parameters" to get to the relevant information that
> you got wrong in the first place - right?
>

Ditto.

>> | But that looks to be beyond your capability, also.
>
> http://www.apps.ietf.org/rfc/rfc3676.html#sec-4.3
> "There is a long-standing convention in Usenet news which also
> commonly appears in Internet mail of using "-- " as the separator line
> between the body and the signature of a message. When generating a
> Format=Flowed message containing a Usenet-style separator before the
> signature, the separator line is sent as-is."
>

Which RFC is that?


> Now where does it state "It needs to be exactly
> hyphen-hyphen-space-newline."
>

In the RFC.  But you can't read either, so we also know you are an idiot.

> [snip]
> -- -----------------------------------------------------------
> "Pr0r3p"<pr0r3p@yahoo.com>  wrote:
> I said I was aiming at your stupidity, not your brain.
>
> "Johnny"<wxpprofessional@msn.com>  writes:
> You missed. You can not hit a non-existent thing.
> -- -----------------------------------------------------------

So, in one post you've proven you are all three.  Good job - even 
"Pointed Head" hasn't managed that.

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

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-20 11:38 -0700
  Re: problem saving date fields Luuk <Luuk@invalid.lan> - 2011-05-20 20:50 +0200
  Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-21 08:58 +1000
    Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-20 22:35 -0400
      Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-21 13:13 +1000
        Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-20 23:47 -0700
          Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-21 00:18 -0700
            Re: problem saving date fields Luuk <Luuk@invalid.lan> - 2011-05-21 09:54 +0200
            Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-21 10:37 -0400
              Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-21 08:07 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-21 19:55 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-22 14:20 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 17:28 -0400
        Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-21 10:32 -0400
          Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-22 02:08 +1000
            Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-21 20:01 -0400
              Re: problem saving date fields "Twayne" <nobody@devnull.spamcop.net> - 2011-05-21 20:30 -0400
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-21 23:13 -0400
              Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-22 14:28 +1000
                Re: problem saving date fields Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-05-22 12:45 +0200
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 08:26 -0400
                Re: problem saving date fields "Twayne" <nobody@devnull.spamcop.net> - 2011-05-22 09:20 -0400
                Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-23 00:08 +1000
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 13:47 -0400
                Re: problem saving date fields Bill B <me@privacy.net> - 2011-05-22 14:17 -0400
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 14:26 -0400
                Re: problem saving date fields Bill B <me@privacy.net> - 2011-05-22 16:27 -0400
                Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-23 09:01 +1000
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 20:21 -0400
                Re: problem saving date fields Bill B <me@privacy.net> - 2011-05-22 21:36 -0400
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 21:46 -0400
                Re: problem saving date fields Jeff North <jnorthau@yahoo.com.au> - 2011-05-23 12:20 +1000
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-22 22:30 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-22 21:51 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-23 07:13 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-23 10:18 -0700
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-23 10:27 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-23 14:16 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-23 12:17 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-23 18:00 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-23 22:30 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-24 05:45 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-26 02:10 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-26 05:43 -0400
                Re: problem saving date fields Co <vonclausowitz@gmail.com> - 2011-05-23 14:26 -0700
                Re: problem saving date fields Jerry Stuckle <jstucklex@attglobal.net> - 2011-05-23 18:01 -0400
                Re: problem saving date fields Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2011-05-23 23:59 +0200
                Re: problem saving date fields "Twayne" <nobody@devnull.spamcop.net> - 2011-05-22 09:11 -0400

csiph-web