Differences between revisions 1 and 24 (spanning 23 versions)
Revision 1 as of 2007-06-15 20:08:02
Size: 40
Editor: anonymous
Comment:
Revision 24 as of 2007-06-16 04:10:11
Size: 1302
Editor: anonymous
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
     * print?, save and show?
     
   * Query class
     * has an instance of the database class as a `parent'
     * has a query string
     * think about recursive searching without actually calling sqlite every time

 * Issues to brainstorm:

   * 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
      • print?, save and show?
    • Query class
      • has an instance of the database class as a `parent'
      • has a query string
      • think about recursive searching without actually calling sqlite every time
  • Issues to brainstorm:
    • 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

days4/projects/database (last edited 2008-11-14 13:42:11 by anonymous)