This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Issue reported by cusomter (look here for more info: http://forums.sun.com/thread.jspa?threadID=5342826&tstart=0). "Insert and Delete in the otherwise promising resultset pane won't work (when inserting, varchar isn't recognized as such, when deleting the engine - wether it's Netbeans or the driver I don't know - tries to prepend a non-existing db-scheme) In the pane that opens when you "view data", click on the leftmost icon to "insert record". Btw, this is the table I've created for testing: CREATE TABLE Test ( Test_ID integer primary key, Name char(50) not null ); First, I cannot omit the primary key which should be possible since "integer primary key" is always AUTO_INCREMENT in sqlite3. Second, Netbeans says: "Please enter valid data for Name of varchar type" when I'm clicking ok. Surrounding with single or double quotes doesn't help either. Lastly, when I toggle null value on the text-field (ctrl + 0), I can click ok but Netbeans says: Error code 0, SQL state nullInsert Commandfailed: no such table: Test.Test -- java.sql.SQLException: no such table: Test.Test One of the drivers with which reproducing the above should be possible is by Xerial (http://www.xerial.org/trac/Xerial/wiki/SQLiteJDBC#Download)."
Thanks for logging this, Roman. How come I'm not seeing these emails - what list is it going to? SQLite is not (currently anyway) a supported database. So it is not a P2 if it doesn't work correctly. But we should make an effort to get this fixed. It's actually two separate issues - can you open a separate issue for the primary key problem?
>Thanks for logging this, Roman. How come I'm not seeing these emails - what list is it going to? It's from the forum. >SQLite is not (currently anyway) a supported database. So it is not a P2 if it doesn't work correctly. Agree, just forgot about this when I spoke with customer. >But we should make an effort to get this fixed. It's actually two separate issues - can you open a separate issue for the primary key problem? Issue #151897.
Since SQLLite is not supported unless the driver report the column is a generated column, we should not handle making the mentioned assumption. So I will not attempt to fix the primary key issue, however I will look into the issue and will try to fix that.
Current SQLLite is not supported database, so no plan for this yet.
NetBeans.org Migration: changing resolution from LATER to WONTFIX