Mysql insert out of order

Question

0.00/5 (No votes)

See more:

First in our system it would not be possible for a user to do this, but a bot (the bot is from facebook from what I can tell from their "vanity" ip) is hitting a page that's missing data in a column that is the primary key but still inserts a row.

This creates problems. One such problem is when I insert a row after their insert, the id inserts that out of order ie, next auto increment should have been 1000 but used id 990. I also saw some bad data echo in the PHP program pulled from the mysql db.

Does anyone know how this can insert with a missing primary and generally how a row can insert out of order? Or any other useful things to consider.

What I have tried:

I added additional code to fail for missing info when trying to insert

Posted 17-Sep-24 4:11am

mcbain19

Add a Solution

1 solution

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)

Dave Kreskowiak · Answer 1 · 2024-09-17T04:47:00

You didn't mention anything about the table structure your inserting records into.

Typically, the primary key is setup to be generated by the database engine when a record is inserted into a table, so no primary key should be specified in that case.

Now, if you have code that is specifying the primary key, it sounds like you're just storing an integer value in a field you're calling the primary key and either letting the user specify the key or your code is generating that value, both are a really bad idea.