|
Size: 696
Comment:
|
Size: 832
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * GOAL: Create a well thought-out SAGE Enhancement Proposal, and start coding to implement it. | * GOAL: SAGE Enhancement Proposal. * Unified database structure for SAGE. * Database class: init establishes connection to sqlite |
| Line 11: | Line 15: |
| * SAGE interface to sqlite | * SAGE [http://www.initd.org/pub/software/pysqlite/doc/usage-guide.html interface] to sqlite |
| Line 25: | Line 29: |
| * Automagic caching of computation results, keeping those results in portable objects, making these objects merge-able, etc... | * Automagic caching: keep track of computation results * keeping those results in portable objects, making these objects merge-able, etc... |
Databases
[:days4/projects/: Other SAGE Days 4 Projects]
Robert Miller, David Joyner, Yi Qiang, Emily Kirkman, Tom Boothby
- GOAL: SAGE Enhancement Proposal.
- Unified database structure for SAGE.
- Database class: init establishes connection to sqlite
- Unified database structure for SAGE.
- Issues to brainstorm:
SAGE [http://www.initd.org/pub/software/pysqlite/doc/usage-guide.html interface] to sqlite
- 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?