Mysql Table Overflow Issue

Question

0.00/5 (No votes)

See more:

Mysql Table Overflow Issue:

We have unlimited number of users in our web site. But MYSQL table, we have some limit for the primary key field.

If we use BIGINT as data type then we should store the user records upto "18446744073709551615".

My query is how to store the unlimited records. What is the best solution for solve this issue?

If we use auto increment process in application layer, I think may be problem will occur for simulataneous request.

Posted 15-Aug-13 21:17pm

Shanmuga Sundaram

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mehdi Gholam · Answer 1 · 2013-08-15T22:19:00

Solution 1

You really should not worry about hitting the limit of bigint or even int since you are more likely to run out of disk space before that.

And well before that you will need to re-architect your site to handle the loads.

Posted 15-Aug-13 22:19pm

Mehdi Gholam

walterhevedeich · Answer 2 · 2013-08-15T22:32:00

UUIDs[^] can generate up to 340,282,366,920,938,463,463,374,607,431,768,211,456[^] unique values. However, I think performance will be one of the major concerns here because you will be using 32 bytes, vs. the 8 bytes of BIGINT.

IMHO, the only time that you will be having a problem of reaching the limit of BIGINT is when your database is not normalized.