From root at common-lisp.net Mon Dec 11 07:01:48 2006
From: root at common-lisp.net (root)
Date: Mon, 11 Dec 2006 02:01:48 -0500 (EST)
Subject: [postmodern-devel] Auto-nag: postmodern please update your webpage
Message-ID: <20061211070148.464EF53014@common-lisp.net>
You are being nagged on because you have not created a
sensible default webpage for your project. Please do so or you will
be nagged again next week. All we ask is that you type in something
about the project and perhaps some links to mailinglists etc. See
common-lisp.net/project/clo/sp/index.html for a reasonable template.
Some projects host their webpages somewhere else (eg.
http://common-lisp.net/project/cl-ppcre) and if you're in the same
situation you may put the following in your index.shtml:
Any questions? You can reach the author of this cronjob at
clo-devel at common-lisp.net
Thanks!
From attila.lendvai at gmail.com Mon Dec 25 13:54:19 2006
From: attila.lendvai at gmail.com (Attila Lendvai)
Date: Mon, 25 Dec 2006 14:54:19 +0100
Subject: [postmodern-devel] postmodern, pg, cl-rdbms
Message-ID:
hello list,
i've recently found postmodern on cl.net, and i was wondering that
there seems to be a massive amount of duplication of efforts among the
following projects:
- pg is a long-time postgresql socket based lib:
http://common-lisp.net/project/pg/
- cl-rdbms (our fresh clsql replacement,
http://common-lisp.net/project/cl-rdbms/ ) which aims to be a backend
independent sql lib, just like clsql, with sexp sql syntax ( see
http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-rdbms-cl-rdbms;a=headblob;f=/test.lisp
for a quick impression ). it has a single backend for now, based on
pg.
- and postmodern which is something like a mixture of pg and cl-rdbms
we should bring out the best of these... my first impression of
postmodern is that it's more modern and better organized code then pg
which is good.
and to also write actual suggestions besides to this rant, i'd use
http://common-lisp.net/project/local-time/ as the date/time
abstraction data type. it supports timezones and has a string
parser/printer.
and fyi, trivial-sockets seems to be a dead project. i've tried to
contact the author several times with patches and there wasn't any
response; #lisp is on the same opinion. usocket at least welcomes
patches, but it's not really important if t-s can already do
everything needed.
any toughts?
--
- attila
"- The truth is that I've been too considerate, and so became
unintentionally cruel...
- I understand.
- No, you don't understand! We don't speak the same language!"
(Ingmar Bergman - Smultronst?llet)
From marijnh at gmail.com Tue Dec 26 11:33:00 2006
From: marijnh at gmail.com (Marijn Haverbeke)
Date: Tue, 26 Dec 2006 12:33:00 +0100
Subject: [postmodern-devel] postmodern, pg, cl-rdbms
In-Reply-To:
References:
Message-ID:
Hello Attila,
I was aware of PG when I wrote Postmodern -- but as you say, its code is not
in a very good state so I opted to re-write it. I didn't find out about
cl-rdbms until very recently, and since it seemed in a rather expermental
and undocumented state I didn't pay too much heed to it.
The part of Postmodern that does SQL-as-s-expressions is something that I
wrote half a year ago and has been in use at the place where I work for a
while now, so I chose to stick with that instead of similar existing
project. There's also a factor of 'it is more fun to write something myself
than it is to bend existing existing into the shape I need' involved here,
so I (intentionally) did not always make the most 'cost-effective' choices.
I checked out local-time (writing a date/time library was something I'd
rather have avoided), but it did not seem to provide the necessary data
types for representing the various SQL types, and it is Unix-only at the
moment (uses the unix timezone files), and I want to be more portable than
that. -- Of course, optional, unportable support for timezones is better
than no support for them at all, so maybe we could add something like that.
Though I haven't found any real clean way to model optional dependencies in
ASDF yet -- see the hideous #.-hacks in the asd files for cl-postgres and
postmodern. I know there are ASDF extensions for things like that, but
nobody uses them so it's rather inconvenient to require them.
Trivial sockets... I know (you've told me multiple times on IRC), but until
usocket has proper and portable support for byte streams this seems the only
alternative (I'll switch to usocket at the drop of a hat when it gets byte
streams).
Anyway, thanks for the reactions, I'll look a bit further into cl-rdbms as
soon as I have the time, and we'll see if some kind of merging is in order.
But maybe you're better off just using the parts of Postmodern that you need
(cl-postgres) in that project? Or a branch of it, if you must... My
experiences with you in UCW context have kind of suggested that we've got a
bit of a different approach towards library building -- I'm something of a
minimalist, you like to throw in all kind of undeniably neat but very
experimental and expensive features ;)
Regards,
Marijn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: