NYCPHP Meetup

[Chris Bielanski]

Does this mean it might be resolved by altering (if possible) the original
or destination table structures to use datetime data instead of mixing
datetime and timestamp?

> -----Original Message-----
> From: Hans Zaunere [mailto:hans not junk at nyphp.com]
> Sent: Tuesday, April 06, 2004 4:42 PM
> To: NYPHP Talk
> Subject: RE: [nycphp-talk] phpMyadmin's dumps won't import
> into...phpMyAdmin?
> 
> 
> 
> >    `cat_49_added` datetime default NULL,
> >    `cat_49_updated` timestamp(14) NOT NULL,
> 
> Here's the problem...
> 
> The datetime is being exported as a standard datetime string (with the
> spaces, hypens, etc).
> 
> The timestamp column should be exported as a number, such as:
> 
> 20040106130344
> 
> This is why it isn't getting quoted.  Yet, the format that's being
> captured by phpMyAdmin is of the string, per above.  Spaces, but not
> quoted, thus your error.
> 
> Why this is happening I'm not sure.  I'd bet it's a bug in phpMyAdmin.
> To see if it's a problem with mysql or phpmyadmin, run these queries
> just as testers:
> 
> SELECT cat_49_added FROM cat_49 LIMIT 1
> 
> SELECT cat_49_updated FROM cat_49 LIMIT 1
> 
> 
> The results of each should be differently formatted.  Are they?
> 
> H
> _______________________________________________
> talk mailing list
> talk at lists.nyphp.org
> http://lists.nyphp.org/mailman/listinfo/talk
> 

>From hans not junk at nyphp.com  Tue Apr  6 16:47:55 2004
Return-Path: <hans not junk at nyphp.com>
Received: from ehost011-1.exch011.intermedia.net (unknown [64.78.21.3])
	by virtu.nyphp.org (Postfix) with ESMTP id 12752A85E9
	for <talk at lists.nyphp.org>; Tue,  6 Apr 2004 16:47:55 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [nycphp-talk] phpMyadmin's dumps won't import into...phpMyAdmi n?
Date: Tue, 6 Apr 2004 13:47:41 -0700
Message-ID: <41EE526EC2D3C74286415780D3BA9F870142791B at ehost011-1.exch011.intermedia.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [nycphp-talk] phpMyadmin's dumps won't import into...phpMyAdmi n?
Thread-Index: AcQcF+YsAC+2iROdRzOD4LfyZDyGRwAAIzZw
From: "Hans Zaunere" <hans not junk at nyphp.com>
To: "NYPHP Talk" <talk at lists.nyphp.org>
X-BeenThere: talk at lists.nyphp.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: NYPHP Talk <talk at lists.nyphp.org>
List-Id: NYPHP Talk  <talk.lists.nyphp.org>
List-Unsubscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=unsubscribe>
List-Archive: <http://lists.nyphp.org/pipermail/talk>
List-Post: <mailto:talk at lists.nyphp.org>
List-Help: <mailto:talk-request at lists.nyphp.org?subject=help>
List-Subscribe: <http://lists.nyphp.org/mailman/listinfo/talk>,
	<mailto:talk-request at lists.nyphp.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2004 20:47:55 -0000


> Does this mean it might be resolved by altering (if possible)=20
> the original
> or destination table structures to use datetime data instead of mixing
> datetime and timestamp?

That would "fix" it but for the wrong reasons, and potentially break
other dependencies that the column is expected to be a TIMESTAMP (like
timestamping).

H