Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's hard to say much without knowing more about your intent and requirements, but in many situations it would be better to have one or more hash tables (or similar) which contain your dynamically generated objects, and then export symbol(s) for your hash table(s).</p> <p>Here's a hand-wavy example of how this can work. If you can edit and add some more information about your requirements and constraints I'll see if I can be more help.</p> <pre><code>(in-package :cl) (defpackage :package-a (:use :cl) (:export *objects* put get) (:shadow get)) (in-package :package-a) (defvar *objects* (make-hash-table) "Container for dynamically generated objects we want to expose to the package's user.") (defun put (name obj) (setf (gethash name *objects*) obj)) (defun get (name &amp;optional default) (gethash name *objects* default)) ;; Your code can put arbitrary objects into the hash table (put :foo (lambda () :a-thunk)) (put :bar (lambda () :another)) ;; And your users can retrieve them (in-package :cl-user) (use-package :package-a) (funcall (get :foo)) ;; =&gt; :a-thunk </code></pre> <p>I used keywords for the names rather than symbols because keywords aren't local to packages (or, more specifically, they're all local to the <code>keyword</code> package. If you were to instead use <code>'foo</code> and <code>'bar</code> you'd be back to needing to export those symbols, or your user would need to use the package designator when refer to them (e.g. <code>(get 'package-a::foo)</code>).</p> <p>You can also use strings as keys, though in that case you would want to create the table with <code>(make-hash-table :test 'equal)</code>. The default hash table test is <code>#'eql</code>, which doesn't compare strings appropriately. Comparing keywords with <code>#'eql</code> is faster than comparing strings with <code>#'equal</code> (because keywords are a simple pointer comparison, as opposed to the character-by-character comparison necessary for strings) but the difference is likely insignificant unless you have specific reason to think otherwise.</p> <p>This approach provides a better interface for your users, because now your have defined entry points, the opportunity for docstrings, defaults, and easier exploration at the REPL.</p>
    singulars
    1. This table or related slice is empty.
    1. POCommon Lisp: defpackage and exporting symbols that are created programmaticaly
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USjbm
    1. USjbm
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCommon Lisp: defpackage and exporting symbols that are created programmaticaly
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COthank you for your answer, although I guess it is more complicated than I need.
      singulars
      1. PO
      1. USengineerX
    2. COYou should not use `get`, as that is an exported symbol from the `common-lisp` package (the accessor `get` does lookups in symbol property lists).
      singulars
      1. PO
      1. USSvante
    3. CO@Svante, you're right insofar as getting into the details would needlessly complicate the topic under discussion, but in general I don't see any reason not to shadow packages from `cl`. The ability to use names appropriate to your program, regardless of what names others have or haven't used, is a big part of the utility provided by things like Common Lisp's package system. `cl:get` is completely absent from many programs; it would be a shame for "get" to be off-limits anyway.
      singulars
      1. PO
      1. USjbm
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload