|
Size: 40
Comment:
|
Size: 1260
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Describe days4/projects/database here. | = Databases = [:days4/projects/: Other SAGE Days 4 Projects] Robert Miller, David Joyner, Yi Qiang, Emily Kirkman, Tom Boothby * GOAL: SAGE Enhancement Proposal. * unified Database class * init establishes connection to sqlite * create, remove and modify tables * copy method - when should this create a new database file? * print?, save and show? * recursive queries without actually calling sqlite every time * query in place, query that creates a new Database object * Brainless database creation. * SAGE [http://www.initd.org/pub/software/pysqlite/doc/usage-guide.html interface] to sqlite [:sqlite-tutorial: creating your own database using sqlite in sage] * Uniform database approach within sage * Databases distributed with sage * Online databases * cgi web-accessible... * accessible from SAGE, perhaps hosted at sage.math... * SQLite servers? * Automagic caching: keep track of computation results * keeping those results in portable objects, making these objects merge-able, etc... * Licensing: $\exists$ DBGPL? * Noticing identical database entries * Standard databases included with sage should be immutable |
Databases
[:days4/projects/: Other SAGE Days 4 Projects]
Robert Miller, David Joyner, Yi Qiang, Emily Kirkman, Tom Boothby
- GOAL: SAGE Enhancement Proposal.
- unified Database class
- init establishes connection to sqlite
- create, remove and modify tables
- copy method - when should this create a new database file?
- print?, save and show?
- recursive queries without actually calling sqlite every time
- query in place, query that creates a new Database object
- Brainless database creation.
SAGE [http://www.initd.org/pub/software/pysqlite/doc/usage-guide.html interface] to sqlite [:sqlite-tutorial: creating your own database using sqlite in sage]
- Uniform database approach within sage
- Databases distributed with sage
- Online databases
- cgi web-accessible...
- accessible from SAGE, perhaps hosted at sage.math...
- SQLite servers?
- Automagic caching: keep track of computation results
- keeping those results in portable objects, making these objects merge-able, etc...
Licensing: \exists DBGPL?
- Noticing identical database entries
- Standard databases included with sage should be immutable
- unified Database class