Version 1.16.30 is skipping first row when backup db

@milo8080 Did you mean to say “those table will *not* have prefix” ?

Please can you either run the SQL command DESCRIBE TABLE table_name (e.g. in phpMyAdmin) on an affected table, or copy/paste the table definition out of the database backup?

Thank you,
David

Sorry, that’s DESCRIBE table_name (e.g. DESCRIBE wp_some_table).

I experimented something alike and reverted to previous version. Seems to be way better.

On two utf8_general_ci tables where first line was missing, the DESCRIBE command gives:

Field 	 	Type 	 	Null 	Key 	Default 	Extra 	
id 	 	int(11) 	NO 	PRI 	NULL 	 	auto_increment
title 	 	varchar(128) 	YES 		NULL
setting_data 	mediumtext 	YES 		NULL

Field 	Type 	 	Null 	Key 	Default 	Extra 	
id 	smallint(3) 	NO 	PRI 	NULL 	 	auto_increment
label 	varchar(32) 	NO 		NULL

Hope it helps…

Thank you. In the meantime we’ve also discovered the trigger. It happens since version 1.16.30 (i.e. last Thursday’s release) on tables which use signed integers as primary keys. This doesn’t affect any WP core tables, as they all use unsigned integers.

A 1.16.31 release is coming up any moment…

It’s released now. Thanks for the report, and sorry for the trouble!

David

hey @davidanderson, thanks for very quick reply.

By the way I’m using prefixed table. (prefix wp_) and Yes I’m using SIGNED INT as a key. So it should be that the trigger as you said in your previous post… Here is the describe command result of one of those tables:

DESCRIBE wp_testtable;

Field       | Type         | Null | Key  | Default | Extra
------------+--------------+------+------+---------+---------------
id          | int(11)      | NO   | PRI  | NULL    | auto_increment
testingext1 | int(11)      | NO   | NULL |         |
testingext2 | int(11)      | NO   | NULL |         |
stringchar1 | varchar(100) | YES  | NULL |         |

Anyway thanks for your quick fix. I will upgrade updraft plus as soon as possible to the newest version.??