Second guess:
Since you are connected as "admin" at insert time, your row is inserted into
ADMIN.TBLTEST.
On the other hand, if you are connected anonymously to the DB while reading,
chances are you're are using instead APP.TBLTEST at that time.
Of course, this only could happen without error if you have created both
ADMIN.TBLTEST and APP.TBLTEST at some point during your tests. OK, I know that's
a lot of "if"...
Sylvain
Shaffin Bhanji a écrit :
Hello,
Please be patient as I am new to using Derby. I am using the embedded
jdbc driver in my application and it seems that I am able to insert a
row using java without any exceptions but when I browse using the table,
I dont see the new row that I originally inserted. A snipped of my code
looks as follows:
Class.forName( DERBY_DRIVER ).newInstance();
//Get a connection
Connection conn = DriverManager.getConnection(
"jdbc:derby:directory:/home/shaffin/testdb;create=true", "admin",
"password" );
conn.setAutoCommit(true);
PreparedStatement stmt =
conn.prepareStatement("insert into tbltest (fld1, fld2) values(?,?)");
stmt.setString(1, "fld1test");
stmt.setString(2, "fld2test");
c = stmt.executeUpdate();
stmt.close();
conn.close();
Any help is kindly appreciated.
Shaffin.
--
Website: http://www.chicoree.fr
