[prev in list] [next in list] [prev in thread] [next in thread] 

List:       racket-users
Subject:    [plt-scheme] data persistence
From:       bab () entricom ! com (Bruce Butterfield)
Date:       2004-11-29 20:25:14
Message-ID: 41AB85AA.90503 () entricom ! com
[Download RAW message or body]

For my applications the ability to use stored procedures in Postgres 
makes it the db of choice -- as far as I know MySQL still does not have 
this capability. With stored procedures (written in any of several 
flavors including an internal procedural language, PLSQL) I can separate 
  the persistent store from the application logic in a very clean way; I 
can rearrange and optimize my db and its access logic without affecting 
the defined interface. Postgres in general is a much more sophisticated 
environment in which to do serious development.


Doug Orleans wrote:
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
> 
> OK, I think I'm going to bite the bullet and run a real database
> server, because there are enough other things I want to do that would
> probably be easiest that way.  So, what are the relative advantages of
> MySQL, Postgres, etc?  I realize this is a generic database question,
> but since I'll mostly be interacting with it via Scheme I figured it'd
> be okay to ask here.
> 
> --dougo at place.org


[prev in list] [next in list] [prev in thread] [next in thread]