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. One of the drivers with which reproducing the above should be possible is by Xerial (http://www.xerial.org/trac/Xerial/wiki/SQLiteJDBC#Download)."
SQLite is not currently
SQLite is not currently supported. The JDBC driver for SQLite does not report that a primary key is auto-increment, so our code doesn't detect it. We would need to add specialized support for SQLite. I don't know why the varchar doesn't work, that's a real problem.
varchar issue will be fixed part of another issue. But the primary key cannot be omit with SQLite, can't be fixed since the driver does not report it properly and I don't want to write any custom code for non-supported database.
Ahi, I agree that it can be hard to fix, but it is customer reported issue and it seems that SQLite becomes more and more popular. Lets see on this issue in the future, not for next release, probably this DB become popular in nearest future and then it will be much better to fix this issue. Now lets mark this issue as RESOLVED LATER.
Will pay attention in the future.
I agree with Roman. I am planning a number of places where I have special-case code for popular database vendors. JDBC drivers are notorious in terms of their inconsistent implementation of the spec. It's just the way it is. I would prefer you not resolve it with LATER but set the target milestone to next, given that it's a user-requested feature and I agree with Roman, sqlite is becoming more and more popular. I just wish its JDBC driver were more compliant.
NetBeans.org Migration: changing resolution from LATER to WONTFIX