1062 Duplicate entry '2147483647' for key 1

[dmm2020]

HELP!!!

I am getting 1062 Duplicate entry '2147483647' for key 1 when a customer attempts to confirm any order. It appears that the roder id is stuck on this number and not autoincrementing. I search the threads and can't find the solution for this and it is rather urgent as my website is virtually shut down because of this error.

Please advise.

[Kim]

Did you modify/reset the order numbers to be a huge number?

( look in the similiar threads section at the bottom of this page for more information)

[dmm2020]

Did you modify/reset the order numbers to be a huge number?

( look in the similiar threads section at the bottom of this page for more information)

Nope well kinda, but the behavior of that is not what you would expect... once I tested successful orders, I set the counter to 2008999999, but the very next order the order number was 2147483647 which is the max mysql auto increment for int(11) fields.

I deleted the table data through phpMyAdmin and reset the counters to 1. I wanted the orders to be in 8-10 digit format, but appears it will not work with Zen Cart.

I went through previous posts and that is like looking for a needle in a haystack for the answer, plus too many off-topic responses and similiar but unrelated posts make it next to impossible to find what I need.

[Kim]

I wanted the orders to be in 8-10 digit format,

Why do you think you need such a large format?

[dmm2020]

Why do you think you need such a large format?

Looking for a way to assign numbers based on the year they are initiated in. I don't have to go that big, just what I did to make the error happen.

I run a software download site for Arcadem Pro arcade game script and the potential for high number of orders in such a targeted website is huge. Especially when I am currently the only one besides Agares Media to legally make the software downloadable. So I wanted to start out with potential for the number of orders in a year to be upto 1 million orders. The free software orders will take the bulk of that.

[DrByte]

If that's important to you, I would suggest using a 1-digit year code, instead of 4 digits.
Or, simply edit the code (numerous places) to always output a prefix on all order numbers, and then change that prefix from time to time, ie: annually.

[Kim]

The order numbers are meant to be a simple auto-incremented number. You can do some custom coding to append a certain fixed number to the order number though.

[dmm2020]

The order numbers are meant to be a simple auto-incremented number. You can do some custom coding to append a certain fixed number to the order number though.

Probably do that later through two new fields. One with a prefix and one with order number linked to a master table which shows the next order number to be used. I would need the order number to restart at one at the change of the new year.

[DrByte]

The upcoming v2.0 has some built-in support for prefixes and suffixes on order number displays ... however it is intended more for distinguishing orders in one store from orders in another store moreso than injecting a certain sequence during certain times of the year.

[ShoesBuyOnline]

I have encounter a same problem. I resolved it using below fomula: yymmdd+4 random digits:

$t1 = date("ymd");
srand ((float) microtime() * 10000000);
$input = array ("1", "2", "3", "4", "5", "6", "7", "8", "9", "0");
$rand_keys = array_rand ($input, 3);
$l1 = $input[$rand_keys[0]];
$l2 = $input[$rand_keys[1]];
$l3 = $input[$rand_keys[2]];
$r1 = rand(0,9);

$ordernum = $t1.$l1.$l2.$l3.$r1;

Wish this would help,