Oracle Express Edition is identical to enterprise editions, with only license and capacity limitations (base size, number of users, concurrent performance, etc.).
The problem you are experiencing is because Oracle's default behavior is implicitly initiate a transaction upon receiving a insert , delete , update ).
This transaction implicitly started needs to be explicitly terminated (with a commit or rollover command), otherwise Oracle will automatically > rollback at the end of the session (when you disconnect).
This behavior is not the default for all DBMSs . Microsoft SQL Server, for example, implicitly initiates and commits a transaction to each data manipulation command, as long as the user has not explicitly started the transaction (if the user initiates the transaction explicitly he also needs to commit explicitly).
So, to solve your problem, after inserting a record, execute the commit command, so the transaction will take effect and the log will be available to other users (other connections).
This default behavior can also be changed by server or session configuration, but is generally not a good idea.
The graphical interface is a separate database server tool, and there are several available, such as Oracle SQL Developer and SQuirreL SQL Client .