These days encountered two problems, are very wonderful, distressed for three days, the final positioning out.
Problem one, inserting data through PL/SQL developer to a remote Oracle database server, querying data through PL/SQL developer queries, but not data through remote Oracle Sqlplus The application does not find data through MyBatis queries.
After the problem occurred, because I mybatis unfamiliar, has been suspected of grammar and configuration in addition to the problem, positioning problems have been in these two directions, from the official documents, grammar is no problem, but still in accordance with their own doubts of various changes, various tests, has been suspected to be able to query the results, is the MyBatis conversion Java object when the problem, later debugging into the root, JDBC access to data, or no data, the final judgment is not mybatis out the problem, the problem is in the data preset place, re-through the server Sqlplus preset data, Data this query out. This concludes that PL/SQL developer itself caches the new data and is not plugged into the server. Problem solving.
Problem two, through the application query to insert data, but the query when the query does not come out, through the PL/SQL developer query is also not out, but on the remote Oracle server through Sqlplus can be queried.
There was a problem with the application query, and the statement that initiated the query list was not executed. Or is it through PL/SQL Developer new table structure to the remote Oracle server, because the entity beans in the app and the field types in the database do not match. can cause problems with query data. By solving the problem, it is concluded that PL/SQL developer caches the table structure and table data. Also found a phenomenon is that the first connection although can be connected, but the execution of the SQL button Gray, and then through his connection to other databases, button shiny, switch to the previous database, the button is shiny, this process, also shows that PL/SQL developer is problematic. PL/SQL Developer cache the table structure and data.
The scenario is this:
Project Architecture is SPRING+MYBATIS+TK.MYBATIS+SPRINGMVC
Using the MyBatis Extension tool Tk.mybatis eliminates the usual additions and deletions to redundant code, because the MyBatis syntax is not very familiar with, has been suspected to be
Using MyBatis queries, and querying data in t_product_info tables using PL/SQL
The main possible cause should be inconsistencies in data structures before and after the insert. Resolution by deleting the table to reconstruct the data.
There is data in the Oracle database, which cannot be queried by PL/SQL and can be found with sqlplus, and PL/SQL developer caches the data locally