2 ms·
> For example, we have dynamic programming languages, but not dynamic RDBMS (that use SQL or a close variation). Why not? Depending on what you mean, SQLite is
by samatman 7y ago
> For example, we have dynamic programming languages, but not dynamic RDBMS (that use SQL or a close variation). Why not?
Depending on what you mean, SQLite is exactly this.
It is relational, so one does have to structure tables, but I consider this equivalent to naming variables.
Unlike most (all?) other SQL databases, however, the 'types' of the data are just suggestions, and have some influence on how SQLite stores and retrieves them internally.
But you can put a string in an INTEGER field, SQLite won't stop you.
- tabtab 7y agoBut you have to pre-specify the columns. In a truly dynamic DB, you could enter "INSERT INTO foo (myNewColumn) VALUES (123)" and both the table "foo" and "myNewColumn" are created on the fly. SqlLite doesn't do this. Further, one could add restrictions as needed to "lock down" both new column creation, and add type-like validation ("parse" check). Thus, as requirements solidify, it can act more like a traditional RDBMS.