ent: Monday, July 26, 2010 10:08 AM
> To: NYPHP Talk
> Subject: Re: [nyphp-talk] phpMyAdmin and MySQL DB Backup
>
> Peter:
>
> On Sat, Jul 24, 2010 at 12:55:21PM -0400, Peter Sawczynec wrote:
>
> > understand one way to get around this all is to remove the record
> with
Peter:
On Sat, Jul 24, 2010 at 12:55:21PM -0400, Peter Sawczynec wrote:
> understand one way to get around this all is to remove the record with the
> autoincrement value of 0. After that this mode would no longer be needed.
> IIRC
> you cannot simply edit an autoincrement field (by design), so
-Original Message-
From: talk-boun...@lists.nyphp.org [mailto:talk-boun...@lists.nyphp.org] On
Behalf Of David Krings
Sent: Saturday, July 24, 2010 12:26 PM
To: NYPHP Talk
Subject: Re: [nyphp-talk] phpMyAdmin and MySQL DB Backup
On 7/24/2010 10:47, Peter Sawczynec wrote:
> Okay, here
On 7/24/2010 10:47, Peter Sawczynec wrote:
Okay, here is an issue that is not straight PHP related, but close and I
really could use some good feedback.
___
Recently, I have had a DB dump/backup (created using the phpMyAdmin interface)
fail because there is a single table in this db tha
> Recently, I have had a DB dump/backup (created using the phpMyAdmin
> interface) fail because there is a single table in this db that needs
> this exception written into the backup file output: "SET
> SQL_MODE="NO_AUTO_VALUE_ON_ZERO";"
>
> It seems, the phpMyAdmin interface does not have an opt
Okay, here is an issue that is not straight PHP related, but close and I
really could use some good feedback.
___
Recently, I have had a DB dump/backup (created using the phpMyAdmin
interface) fail because there is a single table in this db that needs this
exception written into the ba
