Mercurial > hg > amuse
diff base/database/generics.lisp @ 309:7038c3dc0a5a
Add some generic functions for querying the database in amuse-database-admin.
Ignore-this: d2516f9e731f2e7a079d8a094c70e927
How much general functionality should there be here?
The basic idea is a generalisation of mtp-admin, but there is a lot still to do.
darcs-hash:20100223150341-16a00-46cb41323450b18e21a4fff2cdaf7d38e9c572dc.gz
author | j.forth <j.forth@gold.ac.uk> |
---|---|
date | Tue, 23 Feb 2010 15:03:41 +0000 |
parents | 00d35eb70ef9 |
children | 6a3adca16910 |
line wrap: on
line diff
--- a/base/database/generics.lisp Fri Feb 12 10:19:00 2010 +0000 +++ b/base/database/generics.lisp Tue Feb 23 15:03:41 2010 +0000 @@ -1,3 +1,24 @@ (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))