Mercurial > hg > amuse
view base/database/generics.lisp @ 310:f99fd6a7bbfc
Add midi-db.
Ignore-this: c6f4fc32efa4453ddbdc478793eedd52
A basic implementation for working with MIDI files stored in the database.
It is a test case for `versioned' data, but only partially implemented at the moment.
darcs-hash:20100223152703-16a00-4388d2720907d777a1c6c6b3a010885ce0fe06a7.gz
author | j.forth <j.forth@gold.ac.uk> |
---|---|
date | Tue, 23 Feb 2010 15:27:03 +0000 |
parents | 7038c3dc0a5a |
children | 6a3adca16910 |
line wrap: on
line source
(cl:in-package #:amuse-database-admin) (defgeneric make-composition-identifier (package composition-id)) ;;;==================================================================== ;;; Generic functions for querying the database ;;; ;;; FIXME: how sane is this? The idea was to have a general mtp-admin. ;;; ;;; What about arbitrary SQL conditions? Might be useful for general ;;; searching, and defining new datasets (which I currently do by ;;; writing the resuls of a SQL query to a file (e.g. `all the Beatles ;;; songs'), and then reading the file into lisp). Amuse-midi-db ;;; implements these methods. ;;; ;;; Also, should this kind of generality be extended to data import ;;; and export? ;;; ===================================================================== (defgeneric list-collections (package-object &key compositions stream)) (defgeneric list-compositions (package-object &key collection-identifier stream))