Difference between revisions of "SQLite Adapter Research"
Cwdesautels (talk | contribs) |
Cwdesautels (talk | contribs) |
||
| Line 14: | Line 14: | ||
|- | |- | ||
|Number of columns | |Number of columns | ||
| − | | | + | |Default: 2000 \n Max: 32767 |
|- | |- | ||
|Number of rows | |Number of rows | ||
| Line 22: | Line 22: | ||
| | | | ||
|- | |- | ||
| + | |Database size | ||
| + | | | ||
| + | |- | ||
| + | |Max number of columns | ||
| + | | | ||
| + | |- | ||
| + | |UUID & Auto Increment | ||
| | | | ||
| + | |- | ||
| + | |Joins | ||
| | | | ||
|} | |} | ||
| − | |||
Revision as of 21:38, 22 September 2011
Overview
Data Types
http://www.sqlite.org/datatype3.html Most SQL database engines (every SQL database engine other than SQLite, as far as we know) uses static, rigid typing. With static typing, the datatype of a value is determined by its container - the particular column in which the value is stored.
SQLite uses a more general dynamic type system. In SQLite, the datatype of a value is associated with the value itself, not with its container. The dynamic type system of SQLite is backwards compatible with the more common static type systems of other database engines in the sense that SQL statement that work on statically typed databases should work the same way in SQLite. However, the dynamic typing in SQLite allows it to do things which are not possible in traditional rigidly typed databases.
Limits
| Feature | Limit |
|---|---|
| Number of columns | Default: 2000 \n Max: 32767 |
| Number of rows | |
| Page size | |
| Database size | |
| Max number of columns | |
| UUID & Auto Increment | |
| Joins |
