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

[postmodern-devel] Table extra options in DAO definition
by Rafał Strzaliński 14 Jul '08

14 Jul '08

Hi, I'm attaching a patch that allows to add table extra options ( :check :unique ..) to a DAO definition. Sample: (defclass account () ((id :col-type serial ) (login :col-type (varchar 255) :accessor login :initarg :login) (password :col-type (varchar 255) :accessor password :initarg :password) (created_at :col-type timestamp :accessor created-at :initform (now-timestamp))) (:unique name) (:metaclass dao-class) (:keys id) (:extra-options (:unique login)) (:table-name account.account)) -- Best regards, Rafal Strzalinski (nabla) http://nablaone.net

2 4

[postmodern-devel] FULL OUTER JOIN clause in s-sql (:outer-join)
by Timur Sufiev 04 Jul '08

04 Jul '08

I've noticed recently that :outer-join spec isn't supported by s-sql, although it is mentioned in reference for postmodern-1.12. So i've added it myself.

2 2

[postmodern-devel] prepare macro syntax
by Roman Budzianowski 19 Jun '08

19 Jun '08

Hi Marijn, (prepare q) where q is bound to a query works fine, however (prepare (get 'foo 'query)) doesn't complain, but generates incorrect closure. Easy workaround, but is this a bug? Thanks, Roman

2 3

[postmodern-devel] the reason why i'd like an iolib network backend instead of usocket
by Attila Lendvai 19 Jun '08

19 Jun '08

dear list, after some uptime, all of a sudden i was getting these errors on our server. this is probably something going awry inside sb-bsd-sockets. as time permits, i'll experiment with an iolib based network backend for cl-postgres. - attila *** At: 2008-06-14T03:47:32.266936+02:00 *** In thread: http worker 34 / serving request / CALL-WITH-SERVER-ERROR-HANDLER / HANDLE-TOPLEVEL-CONDITION *** Error: Socket error in \"socket\": EPROTONOSUPPORT (Protocol not supported) *** Backtrace is: 000: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> #<ESEHO-PRESENTATION::ESEHO-APPLICATION \" /\" {911C645}> #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 001: ((HU.DWIM.WUI:HANDLE-TOPLEVEL-CONDITION :AROUND (T T)) #<ESEHO-PRESENTATION::ESEHO-APPLICATION \"/\" {911C645}> #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 002: ((FLET HU.DWIM.WUI::HANDLE-REQUEST-ERROR) #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 003: ((LAMBDA (ERROR)) #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 004: (SIGNAL #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) [:EXTERNAL] 005: (ERROR SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR) [:EXTERNAL] 006: (SB-BSD-SOCKETS:SOCKET-ERROR \"socket\") 007: (SB-BSD-SOCKETS:SOCKET-ERROR \"socket\") [:EXTERNAL] 008: ((SHARED-INITIALIZE :AFTER (SB-BSD-SOCKETS:SOCKET T)) #<error printing object: NIL>) [:EXTERNAL] 009: ((LAMBDA ())) 010: (USOCKET:SOCKET-CONNECT \"database\" 5432) [:EXTERNAL] 011: (CL-POSTGRES::INITIATE-CONNECTION #<CL-POSTGRES:DATABASE-CONNECTION {107C3F11}>) 012: (CL-POSTGRES:OPEN-DATABASE \"eseho\" \"eseho\" \"szupertitok\" \"database\" 5432 :NO) 013: ((CL-RDBMS.POSTGRESQL::CONNECTION-OF :AROUND (CL-RDBMS.POSTGRESQL::POSTGRESQL-POSTMODERN-TRANSACTION)) #<DWIM-META-MODEL::TRANSACTION :begin-executed-p #t {107AB379}>) 0

2 1

[postmodern-devel] db-null problem
by Roman Budzianowski 12 Jun '08

12 Jun '08

There seems to be a problem with exporting of 'db-null type: CL-USER> (pomo:sql (:create-table foo ((age :type (or db-null integer) :default :null)))) "CREATE TABLE foo (age OR NOT NULL DEFAULT NULL)" =========> error! CL-USER> (in-package :pomo) #<The POSTMODERN package> POMO> (pomo:sql (:create-table foo ((age :type (or db-null integer) :default :null)))) "CREATE TABLE foo (age INTEGER DEFAULT NULL)" POMO> Roman

2 1

[postmodern-devel] sql-op :raw
by Roman Budzianowski 06 Jun '08

06 Jun '08

Hi Marijn, The following fails: (sql (:DROP-TABLE 'MANUFACTURERS (:RAW "cascade"))) with Passed 1 too many arguments for arglist (S-SQL::NAME) Is :raw applicable only in certain contexts? Obviously this is just example - I am trying to build it in run time. Thanks, Roman

2 1

[postmodern-devel] dao functionality
by Roman Budzianowski 05 Jun '08

05 Jun '08

Hi everybody, I have decided to use the postmodern library to basically dump and then keep updating a large in memory object database into Postgres. I am coming from the lisp side (my knowledge of rdb is limited). I am wondering if the dao metaclass would allow me to define a table like the 'enemy' example. In particular is it possible to specify :foreign-key? I don't intend to keep my objects in memory using dao class. I just want to use it to create tables and then to do inserts and updates. Should I use S-SQL and sql-compile instead? Thanks, Roman

2 1

[postmodern-devel] Guarding against DB-NULL from other packages in :CREATE-TABLE
by J.P. Larocque 10 May '08

10 May '08

Hi, I'm defining tables with Postmodern and made the mistake of specifying a column type such as (OR TEXT DB-NULL), where DB-NULL was a symbol newly interned into my current package rather than the symbol in the S-SQL package. This resulted in SQL expressions with illegal syntax being generated (e.g. "column_name OR NOT NULL"). After tracking down the problem and finding it was my fault, I made changes (attached) to catch column-type errors earlier. The patch signals an error in DEF-SQL-OP :CREATE-TABLE when a column type is a list which begins with OR and does not meet the other original criteria for an or-db-null type: DB-NULL is a member, and length is 3. It also now ensures that DB-NULL doesn't occur twice, or on its own, outside of an OR compound type. I didn't do anything to validate other "compound" types such as NUMERIC. You might find it a bit odd that I format the DB-NULL symbol in my ERROR calls with ~S in the format control string instead of simply putting "DB-NULL" in the string: (error "Illegal compound type for column: ~S~ ~&(Only (~S x ~S) and (~S ~S x) are allowed.)" type 'or 'db-null 'or 'db-null)) This ensures that the S-SQL package name is prefixed to the symbol name--but only if S-SQL was not imported by the current package. This emphasizes to these users that DB-NULL was not imported into their current package and this is probably what their problem is. For instance: Illegal compound type for column: (OR TEXT DB-NULL) (Only (OR x S-SQL) and (OR S-SQL x) are allowed.) [Condition of type SIMPLE-ERROR] -- J.P. Larocque: <jpl(a)thoughtcrime.us>, +1 509 324-2410

2 1

[postmodern-devel] Release 1.12
by Marijn Haverbeke 30 Apr '08

30 Apr '08

Hi list, There is now a version 1.12 of postmodern. It features SSL support, a few rather un-spectacular new features, and less bugs than 1.11. See the docs and the darcsweb for details. Regards, Marijn

1 0

[postmodern-devel] Error when no persistent field
by Sven Van Caekenberghe 21 Apr '08

21 Apr '08

Hi, I defined an object with metaclass dao-class but forgot to add any col- type options, this results in a rather cryptic error that is hard to get out of in LispWorks: P1 10 > (select-dao 'enumeration) Error: The assertion (= (LENGTH POSTMODERN::QUERY-FIELDS) POSTMODERN::N-DAO-FIELDS) failed. 1 (continue) Retry assertion. 2 (abort) Return to level 0. 3 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options P1 11 : 1 > :bq (HARLEQUIN-COMMON-LISP:SUBFUNCTION 1 POSTMODERN::BUILD-ROW-READER) <- CL-POSTGRES::SEND-QUERY <- (HARLEQUIN-COMMON-LISP:SUBFUNCTION (LABELS #:G244377) CL- POSTGRES:EXEC-QUERY) <- CL-POSTGRES:EXEC-QUERY <- LET <- EVAL <- CAPI::CAPI-TOP-LEVEL-FUNCTION <- CAPI::INTERACTIVE-PANE-TOP- LOOP <- (HARLEQUIN-COMMON-LISP:SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK) I can live with this, but maybe it would be good to make this more user friendly. Cheers, Sven

2 4

[postmodern-devel] Timestamp (with time zone)
by Sven Van Caekenberghe 14 Apr '08

14 Apr '08

Hi, This is partly postmodern, partly postgresql related. I was wondering whether it would not be useful to also do the following when loading simple-date above postmodern: (in-package :simple-date) (cl-postgres:set-sql-datetime-readers :timestamp-with-timezone (lambda (usecs) (multiple-value-bind (days usecs) (floor usecs +usecs-in-one-day+) (make-instance 'timestamp :days (+ days +postgres-day-offset+) :ms (floor usecs 1000))))) Or even in place of the normal :timestamp binding (from which the above code is copied) ? From my experiments and reading, using timestamp with time zone as SQL type is more useful than timestamp. What I want is a created or last-modified timestamp that is set or updated automatically by SQL and not CL with a default like now(). The problem seems to be that the way now() is interpreted is dependent on the time zone set for the session (or the time zone default of postgresql, which defaults to your machine's). The only correct thing to store are GMT timestamps and to adjust those to the viewer's own time zone. psql does that correctly only with the type timestamp with time zone and not with the type timestamp, although they seem to be the same thing internally. In CL, (simple-date:universal-time-to-timestamp (get-universal-time)) is always GMT, indepedent of the current (viewer's) timezone. In PG SQL this seems to be hard to do using now() or similar functions. So out of the box reader support for that type would be useful. A second question is how to correctly specify this col-type in a DAO since :timestamp-with-time-zone doesn't generate the necessary spaces when generating the table definition and a string is not considered a CL type ? Any thoughts ? Thanks, Sven

2 2

[postmodern-devel] s-sql insert-into problem
by Jens Teich 14 Apr '08

14 Apr '08

I have a tablename as string, a list of fieldnames as strings and a list of values known only at runtime all. Tried the following. What is going wrong? HB> (sql (append (list :insert-into (intern "table") :set) (loop for k in '("field1" "field2" "field3") for v in '(4 5 6) append (list (intern k) v)))) Error: Value (:INSERT-INTO |table| :SET |field1| 4 |field2| 5 |field3| 6) can not be converted to an SQL literal. [Condition of type SIMPLE-ERROR] Jens

2 2

[postmodern-devel] Release 1.11 [was: Unexpected Result from SET command]
by Marijn Haverbeke 09 Apr '08

09 Apr '08

Hey list, I've just released version 1.11 of Postmodern. Mostly bug-fixes, but one feature to be careful with is the new auto-escaping: If you were using 'true and 'false in your queries for boolean values, they will now be escaped and not be read as boolean values at all, so use T and NIL instead. See http://common-lisp.net/project/postmodern for a slightly more detailed release description and, as always, the darcsweb for the definite word on what happened. Regards, Marijn On Tue, Apr 1, 2008 at 5:13 PM, Sven Van Caekenberghe <scaekenberghe(a)common-lisp.net> wrote: > Marijn, > > > > On 01 Apr 2008, at 15:47, Marijn Haverbeke wrote: > > > > Hey Sven, > > > > > > > POSTMODERN 45 > (execute "set time zone gmt") > > > CL-POSTGRES: set time zone gmt > > > Error: Postgresql protocol error: Unexpected message received: S > > > > > > > Oops - this was a case in the pg client/server protocol that I was not > > handling correctly. I've pushed a patch which should solve the > > problem. > > > > Cheers, > > Marijn > > > > Pulling from > "http://common-lisp.net/project/postmodern/darcs/postmodern"... > > Tue Apr 1 15:39:53 CEST 2008 marijnh(a)gmail.com > * handle ParameterStatus messages when reading in query results > > And it works for me now! Thanks a lot for the fast response. > > Regards, > > > > Sven > > > _______________________________________________ > postmodern-devel mailing list > postmodern-devel(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel >

1 0

[postmodern-devel] Unexpected Result from SET command
by Sven Van Caekenberghe 01 Apr '08

01 Apr '08

Hi, Is it possible that there is something wrong or missing in handling the result from a SET command ? POSTMODERN 44 > (connect-toplevel "test" "postgres" "" "localhost") POSTMODERN 45 > (execute "set time zone gmt") CL-POSTGRES: set time zone gmt Error: Postgresql protocol error: Unexpected message received: S 1 (abort) Return to level 0. 2 Return to top loop level 0. Type :b for backtrace, :c <option number> to proceed, or :? for other options POSTMODERN 46 : 1 > :b Call to CL-POSTGRES::LOOK-FOR-ROW Call to CL-POSTGRES::SEND-QUERY Call to (HARLEQUIN-COMMON-LISP:SUBFUNCTION (LABELS #:G135637) EXEC- QUERY) Call to EXEC-QUERY Call to EVAL Call to CAPI::CAPI-TOP-LEVEL-FUNCTION Call to CAPI::INTERACTIVE-PANE-TOP-LOOP Call to (HARLEQUIN-COMMON-LISP:SUBFUNCTION MP::PROCESS-SG-FUNCTION MP::INITIALIZE-PROCESS-STACK) Thanks, Sven

2 2

[postmodern-devel] dao and *escape-sql-names-p*
by Gavin Scott 30 Mar '08

30 Mar '08

Hello, It appears that setting *escape-sql-names-p* breaks dao objects a bit. If it is t when defclass is called, calling get-dao on that class will result in an error from build-row-reader like "Field field does not exist in table class TABLE-CLASS", even though field does indeed exist. This is because slot-sql-name will return a quoted copy of the field name due to *escape-sql-names-p*. A fix is to change direct-column-slot's shared-initialize method to use s-sql:make-sql-name rather than to-sql-name; make-sql-name doesn't quote the column name. However, make-sql-name would then need to be exported by s-sql. A somewhat related issue is that the dao documentation example: http://common-lisp.net/project/postmodern/postmodern.html#daos (defclass user () ... ) has problems if *escape-sql-names-p* is not set since user is an sql keyword. I personally would prefer to see *escape-sql-names-p* set as the default, which would fix this issue. Another solution would be to pick a different example class name or to set *escape-sql-names-p*. Thanks, Gavin Scott gavindscott(a)gmail.com

2 2

[postmodern-devel] Release 1.10
by Marijn Haverbeke 19 Mar '08

19 Mar '08

Hello list, After a lot of bad noise about incompatible changes and a spectacular new DAO system, I now present to you version 1.10 of postmodern. Please take a look -- And do not be afraid to port your code: one large system has already been ported with very little pain. Changes in the interface have turned out to be rather minor. The one subtle point that might bite you is the the way DAO objects are now initialized and saved, so you might want to closely read that part of the documentation. The good news is that the new way things work makes a lot more sense, and is less prone to break down for strange tables and exceptional situations. (Feedback is still appreciated, of course.) Regards, Marijn

1 0

[postmodern-devel] Unbound slots on nullable values?
by Mikko Ahonen 18 Mar '08

18 Mar '08

Hello, I am new to the list, so please forgive me if this is a stupid user error. Am I doing something wrong or is there a bug in how postmodern handles non-null fields? Even very simple dao reports that slot is unbound although according table-description value may be NULL. This is the message I get: The slot TRX is unbound in the object #<KOE {11BA1751}>. I run - Postgres 8.3 - OS X Leopard 10.5.2 - SBCL 1.0.7 - I installed latest postmodern today. I attached output below. Best regards, Mikko Ahonen -- (asdf:oos 'asdf:load-op :postmodern) (use-package :postmodern) ; loading system definition from ; /usr/local/lib/sbcl/site-systems/postmodern.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :POSTMODERN {11E033B9}> as POSTMODERN ; registering #<SYSTEM :POSTMODERN-TESTS {11F4BC91}> as POSTMODERN-TESTS ; loading system definition from ; /usr/local/lib/sbcl/site-systems/bordeaux-threads.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM BORDEAUX-THREADS {120D0031}> as BORDEAUX-THREADS ; registering #<SYSTEM BORDEAUX-THREADS-TEST {11636C29}> as ; BORDEAUX-THREADS-TEST ; loading system definition from /usr/local/lib/sbcl/site-systems/s-sql.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :S-SQL {117B6C01}> as S-SQL ; loading system definition from ; /usr/local/lib/sbcl/site-systems/simple-date.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :SIMPLE-DATE {1191A041}> as SIMPLE-DATE ; registering #<SYSTEM :SIMPLE-DATE-TESTS {11A4BFB1}> as SIMPLE-DATE-TESTS ; loading system definition from ; /usr/local/lib/sbcl/site-systems/cl-postgres.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :CL-POSTGRES {11BDA379}> as CL-POSTGRES ; registering #<SYSTEM :CL-POSTGRES-TESTS {11D181D1}> as CL-POSTGRES-TESTS ; loading system definition from ; /usr/local/lib/sbcl/site-systems/trivial-utf-8.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :TRIVIAL-UTF-8 {11E8E3A1}> as TRIVIAL-UTF-8 ; registering #<SYSTEM :TRIVIAL-UTF-8-TESTS {11FCC3B1}> as TRIVIAL-UTF-8-TESTS ; loading system definition from ; /usr/local/lib/sbcl/site-systems/ieee-floats.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :IEEE-FLOATS {1214B319}> as IEEE-FLOATS ; registering #<SYSTEM :IEEE-FLOATS-TESTS {122CFC91}> as IEEE-FLOATS-TESTS ; loading system definition from /usr/local/lib/sbcl/site-systems/usocket.asd ; into #<PACKAGE "ASDF0"> ; registering #<SYSTEM USOCKET {11783E61}> as USOCKET ; loading system definition from ; /usr/local/lib/sbcl/site-systems/split-sequence.asd into #<PACKAGE "ASDF0"> ; registering #<SYSTEM :SPLIT-SEQUENCE {11938B69}> as SPLIT-SEQUENCE ; loading system definition from /usr/local/lib/sbcl/site-systems/md5.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM MD5 {11ABD991}> as MD5 WARNING: Either there is no Bordeaux-threads support for your implementation, or your implementation does not support threads therefore some features may not work. Feel free to implement it, or bug one of the maintainers to do so if your lisp supports threads at all. STYLE-WARNING: implicitly creating new generic function SOCKET-ACCEPT NIL * T (defparameter *db* "foobar") *DB* (defparameter *db-user* "mikko") *DB-USER* (defparameter *db-pwd* "") *DB-PWD* (defparameter *db-host* "localhost") *DB-HOST* * (connect-toplevel *db* *db-user* *db-pwd* *db-host*) (deftable koe () ((data-id :type integer :initarg :data-id :accessor data-id) (ver :type (or integer db-null) :initarg :ver :accessor ver) (trx :type (or integer db-null) :initarg :trx :accessor trx)) (:class-name koe) (:indices data-id)) * (drop-table 'koe) NIL * (create-table 'koe) WARNING: Postgres warning: CREATE TABLE / PRIMARY KEY will create implicit index "koe_pkey" for table "koe" NIL * (make-instance 'koe :data-id 1 :ver 3) #<KOE {11B3EB71}> * (table-description 'koe) (("data_id" "int4" NIL) ("ver" "int4" T) ("trx" "int4" T)) * (make-instance 'koe :data-id 1 :ver 3) #<KOE {11BA1751}> * (save-dao *) debugger invoked on a UNBOUND-SLOT: The slot TRX is unbound in the object #<KOE {11BA1751}>. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [USE-VALUE ] Return a value as the slot-value. 1: [STORE-VALUE] Store and return a value as the slot-value. 2: [ABORT ] Exit debugger, returning to top level. ((SB-PCL::FAST-METHOD SLOT-UNBOUND (T T T)) #<unavailable argument> #<unavailable argument> #<unavailable argument> #<KOE {11BA1751}> TRX) 0] 2

3 3

[postmodern-devel] postmodern integration
by Attila Lendvai 16 Mar '08

16 Mar '08

dear lists, i've pushed changes into our local-time branch that contains an asdf-system-connection to cl-postgres: darcs pull http://www.common-lisp.net/project/cl-dwim/darcs/local-time Daniel, if you don't mind the extra dependency then please push it into the official. now it's possible to use postmodern so that it returns local-time values and at the same time does not interfere with other softwares that use its simple-date lib. the approach is similar to cl's readtables: (defparameter *custom-sql-readtable* (local-time:set-local-time-cl-postgres-readers (cl-postgres:copy-sql-readtable))) (let ((cl-postgres:*sql-readtable* *custom-sql-readtable*)) (cl-postgres:exec-prepared ...)) at the time of writing our postmodern branch contains a few extra patches. Marijn, please take a look at them and push to the official if you have no concerns with it. darcs pull http://www.common-lisp.net/project/cl-dwim/darcs/postmodern/ -- attila

2 1

[postmodern-devel] Incompatible changes coming up
by Marijn Haverbeke 07 Mar '08

07 Mar '08

Hello list, The next version of Postmodern, 1.10, will include a number of incompatible changes. I have started pushing these changes to the repository, so if you need a stable interface, you should be careful when fetching patches. The repository at http://common-lisp.net/project/postmodern/darcs/postmodern-old holds only backwards-compatible changes. After 1.10 has been properly released and declared stable, I will stop supporting the old interface -- the changes are not that big, and I am too lazy to support multiple branches. So consider yourself warned ;) Cheers, Marijn

1 1

[postmodern-devel] problem with a patch `integer-reader'
by Lars Rune Nøstdal 27 Feb '08

27 Feb '08

Hi, It seems the patch "Sun Nov 11 17:31:19 CET 2007 attila.lendvai(a)gmail.com" is causing some problems when compiling Postmodern on SBCL. As soon as I unpull the patch using darcs the problem goes away and Postmodern compiles. I tried both SBCL-1.0.12 and latest SBCL from CVS -- same problem: CL-USER> (require :postmodern) .. .. ; compiling file "/home/lars/programming/lisp/postmodern/cl-postgres/protocol.lisp" (written 26 FEB 2008 11:08:47 AM): ; compiling (IN-PACKAGE :CL-POSTGRES) ; compiling (DEFINE-CONDITION PROTOCOL-ERROR ...) ; compiling (DEFMACRO MESSAGE-CASE ...) ; compiling (DEFUN READ-BYTE-DELIMITED ...) ; compiling (DEFUN GET-ERROR ...) ; compiling (DEFINE-CONDITION POSTGRESQL-WARNING ...) ; compiling (DEFUN GET-WARNING ...) ; compiling (DEFUN AUTHENTICATE ...) Here is the backtrace: The value NIL is not of type SB-C::NODE. [Condition of type TYPE-ERROR] Restarts: 0: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL {B1C9CA9}> on #<ASDF:CL-SOURCE-FILE "protocol" {B1C9D59}>. 1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {B1C9CA9}> on #<ASDF:CL-SOURCE-FILE "protocol" {B1C9D59}> as having been successful. 2: [ABORT] Return to SLIME's top level. 3: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" {B20BD39}>) Backtrace: 0: (SB-C::NODE-HOME-LAMBDA NIL)[:EXTERNAL] 1: ((LABELS SB-C::FLOOD) #<SB-C::PHYSENV :LAMBDA #<SB-C::CLAMBDA :%SOURCE-NAME SB-C::.ANONYMOUS. :%DEBUG-NAME (SB-C::TL-XEP CL-POSTGRES::AUTHENTICATE) :KIND :EXTERNAL :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID FUNCTION (read-only)> :WHERE-FROM :DEFINED :VARS (#:G251 #:G252 #:G253 #:G254 #:G255) {B3DB279}> :CLOSURE (#<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID STREAM (read-only)> {B38D641}>) {C484619}>) 2: ((LABELS SB-C::FLOOD) #<SB-C::PHYSENV :LAMBDA #<SB-C::CLAMBDA :%SOURCE-NAME CL-POSTGRES::AUTHENTICATE :%DEBUG-NAME NIL :KIND NIL :TYPE #<SB-KERNEL:FUN-TYPE (FUNCTION # #)> :WHERE-FROM :DEFINED :VARS (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) {B363571}> :CLOSURE (#<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID STREAM (read-only)> {B38D641}>) {C484649}>) 3: ((LABELS SB-C::FLOOD) #<SB-C::PHYSENV :LAMBDA #<SB-C::CLAMBDA :%SOURCE-NAME #1=#:G245 :%DEBUG-NAME (LABELS #1#) :KIND NIL :TYPE #<SB-KERNEL:FUN-TYPE (FUNCTION NIL *)> :WHERE-FROM :DEFINED :VARS NIL {B3B5E79}> :CLOSURE (#<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID STREAM (read-only)> {B38D641}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::PARAMETERS :TYPE #<SB-KERNEL:STRUCTURE-CLASSOID HASH-TABLE> {B3639F9}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET {B363399}>) {C484631}>) 4: (SB-C::CLOSE-OVER #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID STREAM (read-only)> {B38D641}> #<SB-C::PHYSENV :LAMBDA #<SB-C::CLAMBDA :%SOURCE-NAME #1=#:G245 :%DEBUG-NAME (LABELS #1#) :KIND NIL :TYPE #<SB-KERNEL:FUN-TYPE (FUNCTION NIL *)> :WHERE-FROM :DEFINED :VARS NIL {B3B5E79}> :CLOSURE (#<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID STREAM (read-only)> {B38D641}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::PARAMETERS :TYPE #<SB-KERNEL:STRUCTURE-CLASSOID HASH-TABLE> {B3639F9}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET {B363399}>) {C484631}> #<SB-C::PHYSENV :LAMBDA #<SB-C::CLAMBDA :%SOURCE-NAME #1=#:G209 :%DEBUG-NAME (LABELS #1#) :KIND NIL :TYPE #<SB-KERNEL:FUN-TYPE (FUNCTION NIL #)> :WHERE-FROM :DEFINED :VARS NIL {B368459}> :CLOSURE (#<SB-C::LAMBDA-VAR :%SOURCE-NAME #:G206 :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID STREAM (read-only)> {B367E51}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::PASSWORD {B363449}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::USER {B3633F1}> #<SB-C::LAMBDA-VAR :%SOURCE-NAME CL-POSTGRES::SOCKET {B363399}>) {C484661}>) 5: (SB-C::%ADD-LAMBDA-VARS-TO-CLOSURES #<SB-C::CLAMBDA :%SOURCE-NAME CL-POSTGRES::READ-UINT4 :%DEBUG-NAME NIL :KIND :LET :TYPE #<SB-KERNEL:BUILT-IN-CLASSOID FUNCTION (read-only)> :WHERE-FROM :DEFINED :VARS (CL-POSTGRES::SOCKET) {B38D7E1}>) 6: (SB-C::ADD-LAMBDA-VARS-AND-LET-VARS-TO-CLOSURES #<SB-C::CLAMBDA :%SOURCE-NAME #1=#:G209 :%DEBUG-NAME (LABELS #1#) :KIND NIL :TYPE #<SB-KERNEL:FUN-TYPE (FUNCTION NIL (VALUES NULL &OPTIONAL))> :WHERE-FROM :DEFINED :VARS NIL {B368459}>) 7: (SB-C::PHYSENV-ANALYZE #<SB-C:COMPONENT :NAME SB-IMPL::ANSI-STREAM-P {B4FB671}>) 8: (SB-C::COMPILE-COMPONENT #<SB-C:COMPONENT :NAME SB-IMPL::ANSI-STREAM-P {B4FB671}>) 9: (SB-C::%COMPILE (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) (BLOCK CL-POSTGRES::AUTHENTICATE (LET # # # # # ...))) #<SB-FASL:FASL-OUTPUT "/home/lars/programming/lisp/postmodern/cl-postgres/protocol.fasl">)[:EXTERNAL] 10: (SB-C::FOPCOMPILE-FUNCTION (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) (BLOCK CL-POSTGRES::AUTHENTICATE (LET # # # # # ...))) (#1=(SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE # #) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION)) #2=(EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) #1#) (PROGN (EVAL-WHEN # #) #2#) SB-C::ORIGINAL-SOURCE-START 0 7) T) 11: (SB-C::FOPCOMPILE (SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) (BLOCK CL-POSTGRES::AUTHENTICATE #)) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION)) (#1=(SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE # #) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION)) #2=(EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) #1#) (PROGN (EVAL-WHEN # #) #2#) SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 12: (SB-C::CONVERT-AND-MAYBE-COMPILE (SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) (BLOCK CL-POSTGRES::AUTHENTICATE #)) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION)) (#1=(SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE # #) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION)) #2=(EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) #1#) (PROGN (EVAL-WHEN # #) #2#) SB-C::ORIGINAL-SOURCE-START 0 7)) 13: ((FLET SB-C::DEFAULT-PROCESSOR) (SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) (BLOCK CL-POSTGRES::AUTHENTICATE #)) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION))) 14: (SB-C::PROCESS-TOPLEVEL-FORM (SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) (BLOCK CL-POSTGRES::AUTHENTICATE #)) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION)) (#1=(EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) (SB-IMPL::%DEFUN # # "Try to initiate a connection. Caller should close the socket if this raises a condition." # #)) (PROGN (EVAL-WHEN # #) #1#) SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 15: (SB-C::PROCESS-TOPLEVEL-PROGN ((SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE # #) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION))) (#1=(EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) (SB-IMPL::%DEFUN # # "Try to initiate a connection. Caller should close the socket if this raises a condition." # #)) (PROGN (EVAL-WHEN # #) #1#) SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 16: (SB-C::PROCESS-TOPLEVEL-FORM (EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) (SB-IMPL::%DEFUN (QUOTE CL-POSTGRES::AUTHENTICATE) (SB-INT:NAMED-LAMBDA CL-POSTGRES::AUTHENTICATE # #) "Try to initiate a connection. Caller should close the socket if this raises a condition." (QUOTE NIL) (SB-C:SOURCE-LOCATION))) ((PROGN (EVAL-WHEN # #) (EVAL-WHEN # #)) SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 17: (SB-C::PROCESS-TOPLEVEL-PROGN ((EVAL-WHEN (:COMPILE-TOPLEVEL) (SB-C:%COMPILER-DEFUN # # T)) (EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) (SB-IMPL::%DEFUN # # "Try to initiate a connection. Caller should close the socket if this raises a condition." # #))) ((PROGN (EVAL-WHEN # #) (EVAL-WHEN # #)) SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 18: (SB-C::PROCESS-TOPLEVEL-FORM (PROGN (EVAL-WHEN (:COMPILE-TOPLEVEL) (SB-C:%COMPILER-DEFUN # # T)) (EVAL-WHEN (:LOAD-TOPLEVEL :EXECUTE) (SB-IMPL::%DEFUN # # "Try to initiate a connection. Caller should close the socket if this raises a condition." # #))) (SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 19: ((FLET SB-C::DEFAULT-PROCESSOR) (DEFUN CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) "Try to initiate a connection. Caller should close the socket if this raises a condition." (LET (#) (CL-POSTGRES::STARTUP-MESSAGE CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::DATABASE) (FORCE-OUTPUT CL-POSTGRES::SOCKET) (LOOP #) (LOOP #) ...))) 20: (SB-C::PROCESS-TOPLEVEL-FORM (DEFUN CL-POSTGRES::AUTHENTICATE (CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::PASSWORD CL-POSTGRES::DATABASE) "Try to initiate a connection. Caller should close the socket if this raises a condition." (LET (#) (CL-POSTGRES::STARTUP-MESSAGE CL-POSTGRES::SOCKET CL-POSTGRES::USER CL-POSTGRES::DATABASE) (FORCE-OUTPUT CL-POSTGRES::SOCKET) (LOOP #) (LOOP #) ...)) (SB-C::ORIGINAL-SOURCE-START 0 7) NIL) 21: (SB-C::SUB-SUB-COMPILE-FILE #<SB-C::SOURCE-INFO >) 22: ((LAMBDA NIL)) 23: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA NIL) {C43F43D}>)[:EXTERNAL] 24: (SB-C::SUB-COMPILE-FILE #<SB-C::SOURCE-INFO >) 25: (COMPILE-FILE #P"/home/lars/programming/lisp/postmodern/cl-postgres/protocol.lisp")[:EXTERNAL] -- Lars Rune Nøstdal http://nostdal.org/

3 3

[postmodern-devel] Re: patches for Postmodern
by Attila Lendvai 26 Feb '08

26 Feb '08

> Looking a bit deeper into the issue of passing values directly to > prepared statements -- one thing we'd have to do first is define some > kind of consistent interface. Right now the rules for what you may > pass in there and how they get treated are completely inconsistent. > I'm not sure how to clean this up without adding overhead or cruft, > though. the following is my mental model about the issue (which is obviously altered by the fact that i use cl-postgres as a backend for cl-rdbms): cl-postgres can send down 4 kind of values to the database: - byte vectors - strings - local-time timestamps (this one is sleazy, see below why) - numbers (this one is sleazy too, because postgresql doesn't know about rationals and converting them to double float under the hood loses precision. i'm not happy about this but it's much more practical then signaling an error and forcing the caller to deal with this all around by doing the same) if your value does not fit in any of these then you must convert it to string yourself before binding it, but it must be done in a higher abstraction layer where (sql) type information is available. an example to demonstrate it is local-time, where the lisp local-time value is used to represent three different db types (timestamp, date, time; where the latter two have constraints on various parts on the local-time value). if you don't care about asserts then you can just local-time:format-rfc3339-timestring the timestamp but it would silently drop information in case of programming errors (e.g. binding a local-time timestamp with non-utc timezone into an sql timestamp without timezone value. postgresql silently ignores the timezone info when doing this). the relevant part of cl-rdbms that deals with this is in execute-postmodern-prepared-statement here: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-rdbms-cl-rdbms;a=… some tests dealing with syntax and types: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-rdbms-cl-rdbms;a=… -- attila

1 0

[postmodern-devel] Using postgresql's default option for column values
by Peter Eddy 11 Feb '08

11 Feb '08

Hi, new postmodern user here. I'd like to be able to use postgresql's 'default' column value feature instead of an :initform in deftable. Is that possible? I haven't had any luck getting it to work. I have a couple of reasons for wanting to do this, first I have several tables that get their primary keys from a single postgresql sequence, e.g.: create table fooA ( id int8 default nextval( 'id_source' ) primary key, ... ) create table fooB ( id int8 default nextval( 'id_source' ) primary key, ... ) Additionally, other table columns use the 'default' option to create creation time stamps and so forth. I can't remove these options from the table definitions because that would break the other applications that use the database. So, what I'm really after is the ability to define fields with deftable so that those fields are not initialized by (make-instance) but read into the dao after creation, similarly to how auto-id appears to work. I looked through the archives but didn't see anything that looked related to this. thanks, Peter

3 5

[postmodern-devel] dynamically built queries
by Ralf Mattes 04 Feb '08

04 Feb '08

Hello list, I need to create queries dynamically and seem to have run into a silly showstopper. I want to create queries like ... SELECT tmp1.name, tmp1.value as "{foo}bar" from baz as tmp1; ... where both the table name alias ("tmp1") as well as the field name alias ("{foo}bar") are _Strings_. Now, if i do: (sql-compile '(:dot "tmp1" value)) --> "E'tmp1'.value" which is definitely _not_ what i want. The same for: (sql-compile '(:as "tmp1" baz)) --> "E'tmp1' AS baz" If possible at all I'd like to avoid the (make-symbol "tmp1") and similar workarrounds. Any ideas? TIA Ralf Mattes

3 3

[postmodern-devel] Release 1.05
by Marijn Haverbeke 16 Jan '08

16 Jan '08

Hello list, Thanks to Ivan's relentless bug finding and feature requesting, version 1.05 of Postmodern is now a reality. See project page (http://common-lisp.net/project/postmodern/) or darcs log (http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=postmodern-postmoder…) for a change list. Enjoy, Marijn

2 2

[postmodern-devel] deftable class-name and unique indices problems
by William Robinson 14 Jan '08

14 Jan '08

Hi. Thanks for the library. I was struggling a bit with pomo's DAO support. A few points: I think it is worth reinforcing in the deftable documentation that a class-name NEEDS to be specified for the data-access methods to function. Can we have/is there a facility for creating unique multi-column indices in deftable? Some more examples for deftable would certainly not go amiss, particularly with repect to usage of :auto-id, :indices and :defer-id. Thanks Bill

2 1