[OPEN-ILS-GENERAL] SQL Repository

[Deanna Frazee]

I ran the “SQL Blood Bank” for Horizon users for several years, and we just put a header on each one that indicated who had created it and, when known, the version of Horizon the creator used.  It worked very well.

 

Deanna Frazee

Killeen City Library System

 

From: open-ils-general-bounces at list.georgialibraries.org [mailto:open-ils-general-bounces at list.georgialibraries.org] On Behalf Of Joe Atzberger
Sent: Saturday, October 03, 2009 1:01 PM
To: Evergreen Discussion Group
Subject: Re: [OPEN-ILS-GENERAL] SQL Repository

 

Just make sure you differentiate what *version* of Evergreen your reports and scripts are written against.  It will not necessarily be portable to other versions.

--Joe

On Sat, Oct 3, 2009 at 12:52 PM, Amy Terlaga <terlaga at biblio.org> wrote:

I guess I was thinking more of the latter, but I don't think the repository should be limited to just simple SQL query examples.  It could be organized by topic, e.g., patrons, items, holds, etc. 

 

There actually already exists a model out there.  The SirsiDynix users group had the SQL Bloodbank (website), that later became a centrally managed wiki for these SQL queries. 

 

Melissa, my email address --  terlaga at biblio.org.  Thanks for sending along some of yours.  

 

Amy

Bibliomation

Middlebury, CT

www.biblio.org


Date: Sat, 03 Oct 2009 10:14:50 -0300
From: "Melissa Belvadi" <mbelvadi at upei.ca>
Subject: [OPEN-ILS-GENERAL] ***SPAM*** Re: SQL Repository?
To: "Evergreen Discussion Group"
   <open-ils-general at list.georgialibraries.org>
Message-ID: <4AC7241A.86CB.008D.0 at groupwise.upei.ca>
Content-Type: text/plain; charset="utf-8"

I agree with Dan about it being pretty broad. But there might be some basic samples that we could share, to offer "best practices".
For instance, when crossing tables, there are two ways - to use "join" or two use explicit "ands" to connect the corresponding columns.
I've done it both ways but notice that when we get sql scripts from Equinox, they always use the "join" syntax, so I'm starting to switch.
Maybe the first thing to establish is whether the intent is to provide complex canned scripts for common functions run regularly, like Conifer's perl scripts, or shorter examples that help to demonstrate the relational structure of the tables for use in making quick one-off queries in something like pgadmin.
Amy, I'd be happy to send you some examples of the latter, if you give me your email address.

Melissa Belvadi

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20091005/d4295831/attachment.htm