Bug #63338 | Primary Key - Not setting the autoincrement choice | ||
---|---|---|---|
Submitted: | 20 Nov 2011 11:18 | Modified: | 21 Dec 2011 21:44 |
Reporter: | Napoleon Tsogas | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.35 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | _id, auto value, autoincrement, primary key |
[20 Nov 2011 11:18]
Napoleon Tsogas
[20 Nov 2011 13:34]
Valeriy Kravchuk
Do you expect to see autoincremented values while adding data in Insert tab in Workbench? Just leave that column empty and server will insert values.
[20 Nov 2011 14:38]
Napoleon Tsogas
[20 Nov 11:18] Napoleon Tsogas Description: I am new on MySQL , so I started from the beging following exactly the instructions. When I created my new table i used the check boxes in order to set what my column will be. At PK i checked the NN and AI as well. Unfortunately when I am going to edit the data the Primary Key is not auto numbered. How to repeat: Autoincrement function [20 Nov 13:34] Valeriy Kravchuk Do you expect to see autoincremented values while adding data in Insert tab in Workbench? Just leave that column empty and server will insert values. Dear Valeriy thank you for your reply, This is my problem when I press ''Now click the Apply changes to data source button '' and is getting me to the sql script and i press Apply i am getting the following message "ERROR 1364: Field 'idMaterials' doesn't have a default value SQL Statement: INSERT INTO `inprima`.`materials` (`TypeMaterial`) VALUES ('Paper')"
[20 Nov 2011 14:46]
Napoleon Tsogas
Yes!!! it worked but not as instructions from "http://dev.mysql.com/doc/workbench/en/wb-getting-started-tutorial-adding-data.html" I need to go forward engineer and the i did sychronize Model and then worked. Thank you again
[21 Nov 2011 21:44]
MySQL Verification Team
Could you please provide the create table statement of the table involved. Thanks.
[22 Dec 2011 7:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".