annotate base/database/generics.lisp @ 316:d9193c44b207
twiddle midi-db import example
Ignore-this: cf975529b1d8ad8af507e7dd2144ccea
darcs-hash:20100416180846-16a00-a91855cc12370a9198448353f4438647d4cdfdae.gz
author |
j.forth <j.forth@gold.ac.uk> |
date |
Fri, 16 Apr 2010 19:08:46 +0100 |
parents |
7038c3dc0a5a |
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))
|