Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm doing something similar. There are a few differences in addition to the ones mentioned that I ran into:</p> <ul> <li><p>in the newer versions of SQLite3 with the Xerial JDBC driver, foreign keys are indeed supported. SQLite supports inline foreign key constraint definition: <br>CREATE TABLE Blah (foreignId Integer REFERENCES OtherTable (id)); <br><br> MySQL (with InnoDB) will <em>accept</em> the same syntax, but won't actually enforce the constraint unless you use a separate FOREIGN KEY clause which explicitly names the foreign table and key column(s): <br> CREATE TABLE Blah (foreignId INTEGER, FOREIGN KEY foreignId REFERENCES OtherTable (id));</p></li> <li><p>old versions of the SQLite JDBC driver don't support Statement.RETURN_GENERATED_KEYS; fixed in newer Xerial drivers.</p></li> <li><p>the syntax for auto-incrementing keys differs; SQLite: (id INTEGER PRIMARY KEY ASC, ...); MySQL: (id INTEGER PRIMARY KEY AUTO_INCREMENT, ...)</p></li> <li><p>SQLite accepts n-way comma-delimited joins: <br> SELECT * FROM A, B, C ON (A.x = B.y AND B.y = C.z); <br><br> MySQL does not; the following works in both: <br> SELECT * FROM A INNER JOIN B ON A.x = B.y INNER JOIN C ON B.y = C.z;</p></li> <li><p>With respect to the type differences, a related annoyance with SQLite's JDBC drivers is that the same column can produce different types via ResultSet.getObject(.); for example, an Integer or a Long depending on the magnitude of the number contained.</p></li> <li><p>auto-incrementing keys in SQLite MUST be declared type INTEGER; in MySQL any numeric integer type works.</p></li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POMySQL and SQLite differences in SQL
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USchris
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COcan you verify which version of sqlite jdbc driver you are using which seems to support RETURN_GENERATED_KEYS ? I have tried many different versions with no luck
      singulars
      1. PO
      1. USAmit
    2. COhttp://www.xerial.org/trac/Xerial/wiki/SQLiteJDBC working at least as of 3.6.20.1
      singulars
      1. PO
      1. USchris
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload