Using the DEFAULT keyword or by omitting the column from the INSERT list: INSERT INTO dataset (id, age, name, description) VALUES (DEFAULT, 42, ‘fred’, ‘desc’); INSERT INTO dataset (age, name, description) VALUES (42, ‘fred’, ‘desc’);
For example, here’s a table that has a primary key but is not AUTO_INCREMENT: mysql> CREATE TABLE foo ( id INT NOT NULL, PRIMARY KEY (id) ); mysql> INSERT INTO foo VALUES (1), (2), (5); You can MODIFY the column to redefine it with the AUTO_INCREMENT option: mysql> ALTER TABLE foo MODIFY COLUMN id INT … Read more
Yes. See here. Section 7.1.9. Change your code to: String sql = “INSERT INTO table (column1, column2) values(?, ?)”; stmt = conn.prepareStatement(sql, Statement.RETURN_GENERATED_KEYS); stmt.executeUpdate(); if(returnLastInsertId) { ResultSet rs = stmt.getGeneratedKeys(); rs.next(); auto_id = rs.getInt(1); }
If you are worried about it growing out of bounds too quickly, I would set the PK as an UNSIGNED BIGINT. That gives you a max value of 18446744073709551615, which should be sufficient.
Jim Martin’s comment from ยง3.6.9. “Using AUTO_INCREMENT” of the MySQL documentation: Just in case there’s any question, the AUTO_INCREMENT field /DOES NOT WRAP/. Once you hit the limit for the field size, INSERTs generate an error. (As per Jeremy Cole) A quick test with MySQL 5.1.45 results in an error of: ERROR 1467 (HY000): Failed … Read more
I have decided for second option – to parse AndroidManifest.xml. Here is working snippet. task(‘increaseVersionCode’) << { def manifestFile = file(“AndroidManifest.xml”) def pattern = Pattern.compile(“versionCode=\”(\\d+)\””) def manifestText = manifestFile.getText() def matcher = pattern.matcher(manifestText) matcher.find() def versionCode = Integer.parseInt(matcher.group(1)) def manifestContent = matcher.replaceAll(“versionCode=\”” + ++versionCode + “\””) manifestFile.write(manifestContent) } tasks.whenTaskAdded { task -> if (task.name == … Read more
From the answer I got here: You can use: SET [GLOBAL|SESSION] sql_mode=”NO_AUTO_VALUE_ON_ZERO” Which as described here, will prevent MySQL from interpreting an INSERT/UPDATE ID of 0 as being the next sequence ID. Such behaviour will be limited to NULL. It is what I’d consider pretty bad behaviour from the application though. You’ll have to be … Read more
That’s how it’s supposed to work – next_val(‘test_id_seq’) is only called when the system needs a value for this column and you have not provided one. If you provide value no such call is performed and consequently the sequence is not “updated”. You could work around this by manually setting the value of the sequence … Read more
It can’t work that way. Consider: program one, you open a transaction and insert into a table FOO which has an autoinc primary key (arbitrarily, we say it gets 557 for its key value). Program two starts, it opens a transaction and inserts into table FOO getting 558. Program two inserts into table BAR which … Read more
What you’re trying to do sounds dangerous, as that’s not the intended use of AUTO_INCREMENT. If you really want to find the lowest unused key value, don’t use AUTO_INCREMENT at all, and manage your keys manually. However, this is NOT a recommended practice. Take a step back and ask “why you need to recycle key … Read more