annotate 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
rev   line source
j@287 1 (cl:in-package #:amuse-database-admin)
j@287 2
j@287 3 (defgeneric make-composition-identifier (package composition-id))
j@309 4
j@309 5
j@309 6 ;;;====================================================================
j@309 7 ;;; Generic functions for querying the database
j@309 8 ;;;
j@309 9 ;;; FIXME: how sane is this? The idea was to have a general mtp-admin.
j@309 10 ;;;
j@309 11 ;;; What about arbitrary SQL conditions? Might be useful for general
j@309 12 ;;; searching, and defining new datasets (which I currently do by
j@309 13 ;;; writing the resuls of a SQL query to a file (e.g. `all the Beatles
j@309 14 ;;; songs'), and then reading the file into lisp). Amuse-midi-db
j@309 15 ;;; implements these methods.
j@309 16 ;;;
j@309 17 ;;; Also, should this kind of generality be extended to data import
j@309 18 ;;; and export?
j@309 19 ;;; =====================================================================
j@309 20
j@309 21 (defgeneric list-collections (package-object &key compositions stream))
j@309 22
j@309 23 (defgeneric list-compositions (package-object &key
j@309 24 collection-identifier stream))