November 2007 - postmodern-devel - mailman3.common-lisp.net

[postmodern-devel] development plans for discussion
by Attila Lendvai 19 Nov '07

19 Nov '07

hi! i have two changes planned: 1) use babel for string encoding/decoding ( http://common-lisp.net/~loliveira/soc07/babel/ ). the rationale is that it's a very nice cross platform unicode lib which is also very fast. Marijn, i hope you will not take it as offense! i know trivial-utf8 is your work, but i hope the speed and the de facto standardness of babel compensates. (Luis will give babel more publicity in the next weeks, but it's available for months now and i'm using it without problems). 2) use iolib for the socket code. i would like to do that because we are experiencing problems when dealing with sockets on sbcl when the system is under heavy load. another reason is that iolib is another nice piece of code, although its also more heavyweight then usocket and also posix-only (currently). i know you prefer simple libs, just like with ironclad/md5, but we need stability and this seems to be the simplest way to achive it. what do you think of these changes? -- attila

2 3

[postmodern-devel] Warnings from bordeaux-threads
by Jens Teich 17 Nov '07

17 Nov '07

I have a problem with warnings from bordeaux-threads. These warnings are no problem when I load manually on Lispworks and SBCL. But when I try to deliver a stand-alone application on Lispworks the delivery process stops at these warnings. I reported the problem to bordeaux-threads mailinglist. They are as follows: | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\bordeaux-threads.ofasl | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\lispworks.ofasl | Warning: (METHOD | MAKE-THREAD | (T)) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). | Warning: (METHOD | MAKE-LOCK | NIL) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). | Warning: (DEFMACRO WITH-LOCK-HELD) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). | Warning: (METHOD | THREAD-YIELD | NIL) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). Is there a way for postmodern to load without bordeux-threads? I think on Lispworks I don't need this. I tried the following (changed t and nil) | ;; Change this to manually turn threading support on or off. | (defparameter *threads* #+(or allegro armedbear cmu corman (and digitool ccl-5.1) | ecl lispworks openmcl sbcl) nil | #-(or allegro armedbear cmu corman (and digitool ccl-5.1) | ecl lispworks openmcl sbcl) t) but there is some resistance: | Loading fasl file d:\Projekte\Lisp\postmodern-1.02\postmodern\connect.ofasl | | Error: Package BORDEAUX-THREADS not found. | 1 Get another package name. | ... Jens

2 2

[postmodern-devel] views
by Joe Corneli 15 Nov '07

15 Nov '07

So, Postmodern doesn't seem to have very minimal support for views (just `list-views' and `view-exists-p'), but I assume I can still work with them? Any tips on that?

3 2

[postmodern-devel] connecting
by Joe Corneli 14 Nov '07

14 Nov '07

I can run psql from the shell -- % psql Welcome to psql 7.4.17, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit joe=# but trying to connect to PostgreSQL with Postmodern currently fails: CL-USER> (connect-toplevel "joe" "joe" "" "localhost") Backtrace: 0: (USOCKET::HANDLE-CONDITION #<SB-BSD-SOCKETS:CONNECTION-REFUSED-ERROR {A7CD821}> #<USOCKET:STREAM-USOCKET {A7B8831}>) 1: (USOCKET:SOCKET-CONNECT "localhost" 5432) 2: (CL-POSTGRES::INITIATE-CONNECTION #<DATABASE-CONNECTION {A7B84C9}>) 3: (CL-POSTGRES:OPEN-DATABASE "joe" "joe" "" "localhost" 5432) 4: (CONNECT-TOPLEVEL "joe" "joe" "" "localhost") 5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CONNECT-TOPLEVEL "joe" "joe" "" "localhost") #<NULL-LEXENV>) Can you give me any ideas on how to get this connection working? This is a fresh install of Postmodern, but I am using some old ASDF files for dependences, do you think that could be the problem?

2 2

[postmodern-devel] Capital/mixed-case table/column names?
by Matthew Lamari 06 Nov '07

06 Nov '07

This question may betray a limited understanding of Postmodern or PostGres; but. . . . If possible, how can Postmodern be used to generate queries that can interact with capitalized/mixed-case table and column names? It appears that in postgres, unless double-quoted, a string is converted to lowercase (as with lisp with uppercase). String literals are single-quoted to SQL literals, not double-quoted as appears required for names. Postgres appears to lowercase even symbols containing capitals (e.g. |AbCd|) If no mechanism for mixed-case exists, would the use of mixed-case symbols be an appropriate change to make to PostGres? Thanks, Matt

2 1