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

cl-postgres convert nil to false
by Julien Danjou 29 Jul '13

29 Jul '13

Hi there, I'm dealing with a problem and I'd like some enlightenment. I've a table with text columns that can't be NULL. In my Lisp program, sometimes I'm assigning `nil' as value for this column, either via a direct query execution or via the DAO. What I would expect in this case, is to PostgreSQL to raise an error. But this does not happen. What happens is that (cl-postgres:to-sql-string nil) returns "false", and that the query is built to: INSERT INTO mytable (mytextfield) VALUES (false); PostgreSQL implicit type conversion kicks in and insert the string 'false' into the field, which does not trigger an error since this it not NULL. The obvious fix here is to patch all my code to convert nil to :null, but this is a pain. I don't want to do the type checking I'm doing with PostgreSQL one more time in my application. What I'd like is for cl-postgres to consider nil as being NULL. The boolean false value could be mapped as :false, which would also make sure no code is inserting false just because a value is actually nil. The change is pretty trivial and I'm running with it right now, which allowed me to debug a lot of implicit nil conversion to 'false' in text fields. I recognize this is something that would break compatibility, so that might be enabled via a defparameter or something. Does that sounds like a good idea, or do I miss an obvious problem? -- Julien Danjou ;; Free Software hacker ; freelance consultant ;; http://julien.danjou.info

2 2

Timezone handling
by Julien Danjou 25 Jul '13

25 Jul '13

Hi there, I'm struggling with timezone handling in Postmodern. I'm using timestamp with time zone column types, and I'm looking for the correct way to feed postmodern such information on insert. Basically, I don't see any class that would fit. I've tried to grep through the code but didn't find much about timestamp/timezone handling. Concretely, I'm having UTC timestamp that I want to insert into those timestamp-with-time-zone columns, but I don't know how to tell Postmodern that it should postfix them with something like +00 so PG understand it should not default them to its default timezone. On the same topic, I thought that one easy solution would be to set the session timezone to UTC. It's easy enough to come with a macro doing a SET TIMEZONE='UTC' before each request, but honestly, I'd like to avoid that and do it only at connection time. Now, I've read through cl-postgres code, and I was hoping being able to plug my code at connection time, but it seems everything is defined as function and not as method, which seems weird to me, and not really pluggable in the end. Any hint appreciated! Cheers, -- Julien Danjou ;; Free Software hacker ; freelance consultant ;; http://julien.danjou.info

3 6

nyef's postmodern gripes
by Zach Beane 25 Jul '13

25 Jul '13

Postmodern fits my needs very well, but whenever it comes up in discussion, nyef has dropped vague disparagement. I pestered him to write down some specifics, so here they are: http://paste.lisp.org/display/138060 Zach

3 2

nyef's postmodern gripes
by Sabra Crolleton 20 Jul '13

20 Jul '13

Is there a better way to write "common table expressions " (with and with recursive) than: (def-sql-op :with (&rest args) (let ((x (butlast args)) (y (last args))) `("WITH " ,@(sql-expand-list x) ,@(sql-expand (car y))))) (def-sql-op :with-recursive (&rest args) (let ((x (butlast args)) (y (last args))) `("WITH RECURSIVE " ,@(sql-expand-list x) ,@(sql-expand (car y))))) They work for me, but I have the feeling there is a better way to do it. Actual use would be something like the following (using the example from the postgresql website): (defun test2 () (query (:with-recursive (:as 'regional-sales (:select 'region (:as (:sum 'amount) 'total-sales) :from 'orders :group-by 'region)) (:as 'top-regions (:select 'region :from 'regional-sales :where (:> 'total-sales (:select (:/ (:sum 'total-sales) 10) :from 'regional-sales)))) (:select 'region 'product (:as (:sum 'quantity) 'product-units) (:as (:sum 'amount) 'product-sales) :from 'orders :where (:in 'region (:select 'region :from 'top-regions)) :group-by 'region 'product)))) Sabra

1 0

[PATCH] Add missing closing parent in example
by Julien Danjou 27 Jun '13

27 Jun '13

--- doc/s-sql.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/s-sql.html b/doc/s-sql.html index a6b0bad..7a8476a 100644 --- a/doc/s-sql.html +++ b/doc/s-sql.html @@ -595,7 +595,7 @@ (age :type integer) (address :type (or db-null string) :references (important-addresses :cascade :cascade)) (fatal-weakness :type text :default "None") - (identifying-color :type (string 20) :unique t) + (identifying-color :type (string 20) :unique t)) (:foreign-key (identifying-color) (colors name)) (:constraint enemy-age-check :check (:> 'age 12)))</pre> -- 1.8.3.1

2 1

simple-date problem
by Jens Teich 16 Apr '13

16 Apr '13

Lispworks 6.1 on Win 7: CL-USER 1 > (asdf :simple-date) ; Loading text file C:\Users\jens\quicklisp\dists\quicklisp\software\postmodern-20130312-git\simple-date.asd ;; Creating system "SIMPLE-DATE->SIMPLE-DATE" ;; Creating system "SIMPLE-DATE" ;; Creating system "SIMPLE-DATE-POSTGRES-GLUE->SIMPLE-DATE" ;; Creating system "SIMPLE-DATE-POSTGRES-GLUE" ;; Creating system "SIMPLE-DATE-TESTS->SIMPLE-DATE" ;; Creating system "SIMPLE-DATE-TESTS" ; Loading fasl file C:\Users\jens\AppData\Local\common-lisp\cache\lw-6.1.1-win-x86\C\Users\jens\quicklisp\dists\quicklisp\software\postmodern-20130312-git\simple-date\simple-date.ofasl #<ASDF:LOAD-OP NIL 21C90697> ((#<ASDF:LOAD-OP NIL 21C90697> . #<ASDF:CL-SOURCE-FILE "simple-date" "simple-date" "simple-date">) (#<ASDF:LOAD-OP NIL 21C90697> . #<ASDF:MODULE "simple-date" "simple-date">) (#<ASDF:LOAD-OP NIL 21C90697> . #<ASDF:SYSTEM "simple-date">)) CL-USER 2 > (in-package :simple-date) #<The SIMPLE-DATE package, 27/64 internal, 19/64 external> SIMPLE-DATE 3 > (encode-timestamp 2013 4 16) #<TIMESTAMP 16-04-2013T00:00:00> SIMPLE-DATE 4 > (timestamp-to-universal-time *) #<pointer out of memory bounds: 1FFB17E7> regards jens

1 0

[postmodern-devel] How can I copy data between a file and a table
by Juan Reynoso Elias 06 Feb '13

06 Feb '13

How can I copy data between a file and a table In postgres I did that : COPY tablex FROM '/tmp/filex.csv'; but in postmodern i don't know. I try (query :copy 'tablex :from "/tmp/filex.csv") -- Juan Reynoso Elias - ikkiware.

2 1

[postmodern-devel] Inserting into an array
by Sabra Crolleton 13 Jan '13

13 Jan '13

I thought I understood the s-sql syntax on inserting into an array. Then I tried it. No, I do not understand the s-sql array syntax for an insert-into statement. Does anyone have a simple example? As a sampe: (query (:create-table test2 ((id :type serial) (name :type text) (stuff1 :type int4[]) (stuff1 :type int4[])))) What would be the equivalent s-sql to (query "insert into test2 values (1,'t2','{22,24,21,20}','{{2,4},{6,7}}')") Such that (query (:select (:[] 'stuff2 1 1) :from 'test2 :where (:= 'id 1)) :single) #2A((2 4)) Thank you for any explanations or pointers. Sabra Crolleton

2 2

[postmodern-devel] Calling a SQL func as a DAO field value
by Julien Danjou 25 Dec '12

25 Dec '12

Hi, I'm trying to use NOW() as a value in an update statement using the DAO. I've tried of syntax combinations, but I can't get the right one. Hint? -- Julien Danjou /* Free Software hacker & freelance http://julien.danjou.info */

2 5

[postmodern-devel] MD5 auth scheme broken?
by Julien Danjou 06 Dec '12

06 Dec '12

Hi there, (I'm new to CL & postmodern, so forgive me in advance.) I tried to use postmodern, but I kept getting: password authentication failed for user "foobar" as error, and I do know that my credentials are ok. Specifying the password as nil in `connect' made me discover that MD5 was used to authenticate. Then, changing 'md5' to 'password' in pg_hba.conf allowed me to connect using postmodern! It seems that the MD5 auth scheme is broken somehow in postmodern, or that I miss something. I'm using PostgreSQL 9.2 FWIW. Hint? -- Julien Danjou -- Free Software hacker & freelance -- http://julien.danjou.info

2 2

[postmodern-devel] Tutorials, examples, and best practices
by Patrick May 21 Nov '12

21 Nov '12

Are there any collections of tutorials, examples, and/or best practices for Postmodern? For instance, I have a macro to wrap database operations: (defmacro with-test-database (&rest body) `(with-connection (list +test-database-name+ +test-database-user+ +test-database-password+ "localhost" :pooled-p t) ,@body)) Obviously it needs some transaction support as well. Do other people use it this way? What are your most useful tips and tricks? Also, it took me some time fiddling around to get :insert-into to work correctly. It makes sense to me now, but a detailed example would have helped. I'm about to write some production code against a mid-sized, fully normalized database. Any lessons learned in those kinds of environments would be of interest. Thanks, Patrick

3 4

[postmodern-devel] Unix socket directory configuration
by Zach Beane 03 Sep '12

03 Sep '12

Hi, I'm trying to use Postmodern on Linux with a Postgres built from scratch. The default value for the Unix socket directory in that situation is /tmp. Postmodern defaults it to /var/run/postgresql, which is more typical for a vendor-packaged Postgres on Linux. It's easy enough to alter/bind cl-postgres::*unix-socket-dir* as needed, but I'm always a little reluctant to use ::. Is that variable a candidate for adding to the supported API by exporting its name? Thanks, Zach

2 2

[postmodern-devel] Errors with MOP operations on dao-class metaclassed object
by Keith Browne 10 Jun '12

10 Jun '12

I'm using Postmodern to query and update a table in a database. The application is networked and threaded, and in the past we've had issues where we get compilation style warnings at run time, and even errors which pop up the debugger. These issues arose when we began flowing client traffic to our application, and I thought that they might be because of some race condition in Postmodern's internals when it starts doing MOP operations on our class which has had (:metaclass dao-class) added to its class definition. Because I suspected a race condition--that multiple threads might be trying to instantiate the MOP stuff around our database accessor class at once--I worked around it by having our startup procedure do a single database access before allowing any client traffic in. That seemed to help things for a while, but this morning I was using the profiler to instrument our code. When I ran the program, and at a point where only that one retrieval should've been running, it popped up with an error in the debugger. I'm using postmodern-20120520-git as loaded through Quicklisp, on SBCL 1.0.57. The issues have arisen on a variety of x86 hardware, both 32- and 64-bits. Here's the defclass for the table in question: (defclass device () ((device-uid :col-type integer :initarg :device-uid :accessor device-uid) (macaddress :col-type string :accessor device-macaddress) (status :col-type string :accessor device-status) (state :col-type string :initarg :state :accessor device-state) (nature :col-type string :accessor device-nature) (client-uid :col-type integer :accessor device-client-uid) (user-uid :col-type integer :accessor device-user-uid)) (:metaclass dao-class) (:keys device-uid)) and here's the function which we call to prime the pump at the start of program execution: (defun get-device-object-by-device-uid (device-uid) (with-connection *db-parameters* (log-message :device-dao-bug "In get-device-object-by-device-uid, device-uid = ~A" device-uid) (let ((result (query (:select '* :from 'device :where (:= 'device-uid device-uid)) (:dao device)))) (log-message :device-dao-bug "Finished query in get-device-object-by-device-uid.") (if result (car result) nil)))) The error I got this morning was: POSTMODERN:DAO-EXISTS-P already names an ordinary function or a macro. [Condition of type SB-INT:SIMPLE-PROGRAM-ERROR] Restarts: 0: [CONTINUE] Replace the function binding 1: [*ABORT] Return to SLIME's top level. 2: [ABORT] Abort thread (#<THREAD "repl-thread" RUNNING {1003E48113}>) Backtrace: 0: (ENSURE-GENERIC-FUNCTION POSTMODERN:DAO-EXISTS-P) 1: (SB-PCL::REAL-ADD-NAMED-METHOD POSTMODERN:DAO-EXISTS-P NIL (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) (POSTMODERN::OBJECT) #<unavailable &REST argument>) 2: (SB-PCL::LOAD-DEFMETHOD-INTERNAL ..) 3: ((LAMBDA ())) 4: ((LAMBDA (SB-INT:&MORE SB-PROFILE::ARG-CONTEXT SB-PROFILE::ARG-COUNT) :IN SB-PROFILE::PROFILE-ENCAPSULATION-LAMBDAS) #<unavailable &MORE argument>) 5: ((LAMBDA (SB-INT:&MORE SB-PROFILE::ARG-CONTEXT SB-PROFILE::ARG-COUNT) :IN SB-PROFILE::PROFILE-ENCAPSULATION-LAMBDAS) #<unavailable &MORE argument>) 6: ((SB-PCL::EMF SB-MOP:FINALIZE-INHERITANCE) #<unavailable argument> #<unavailable argument> #<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) 7: (PROJECT-PACKAGENAME::GET-DEVICE-OBJECT-BY-DEVICE-UID 1) Earlier, when we were allowing multiple threads to access this object at the same time, we got output like this (all of the following is output from one session): debugger invoked on a UNBOUND-SLOT in thread #<THREAD "message handler2" RUNNING {1004843BE3}>: The slot POSTMODERN::COLUMN-MAP is unbound in the object #<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>. STYLE-WARNING: redefining POSTMODERN:DAO-EXISTS-P (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:UPDATE-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:DELETE-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:GET-DAO (#<SB-MOP:EQL-SPECIALIZER {100C80AFB3}>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:INSERT-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN::FETCH-DEFAULTS (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining SHARED-INITIALIZE :AFTER (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE> #<BUILT-IN-CLASS T>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:DAO-EXISTS-P (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:UPDATE-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:DELETE-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:GET-DAO (#<SB-MOP:EQL-SPECIALIZER {100C80AFB3}>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:INSERT-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN::FETCH-DEFAULTS (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining SHARED-INITIALIZE :AFTER (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE> #<BUILT-IN-CLASS T>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:DAO-EXISTS-P (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:UPDATE-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:DELETE-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:GET-DAO (#<SB-MOP:EQL-SPECIALIZER {100C80AFB3}>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN:INSERT-DAO (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining POSTMODERN::FETCH-DEFAULTS (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE>) in DEFMETHOD STYLE-WARNING: redefining SHARED-INITIALIZE :AFTER (#<POSTMODERN:DAO-CLASS PROJECT-PACKAGENAME:DEVICE> #<BUILT-IN-CLASS T>) in DEFMETHOD For the time being, we're planning to work around this by avoiding the use of the dao-class metaclass; we'll write our database queries to return lists or alists, and we'll write update operations directly as SQL or S-SQL queries instead of using update-dao. If there's a way to address this problem and continue using the dao-class metaclass, though, we'd rather do that. Any advice would be most welcome. Keith Browne

1 0

[postmodern-devel] S-SQL extension :if=
by Andy Chambers 14 May '12

14 May '12

Hi All, If anyone's interested in using it, I made a little S-SQL extension (def-sql-op :=if (a b) `(,@(case a (:null (sql-expand `(:is-null ,b))) (nil (sql-expand t)) (otherwise (sql-expand `(:= ,a ,b)))))) I find it convenient when writing queries that take optional parameters where if the parameter is not specified, you want to return the row regardless of what value b takes. Does anyone else write little extensions like these? Should we collect them in a contrib? -- Andy Chambers Software Engineer (e) achambers(a)mcna.net (t) 954-682-0573 CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you.

2 1

[postmodern-devel] single-key object magic
by Greg Pfeil 09 May '12

09 May '12

I've made a few changes to Postmodern. They both try to do a little magic in the case where a table has a single primary key column. The first change allows you to use a DAO-OBJECT directly as a parameter, rather than pulling out the key field. EG: > (select-dao 'foo (:= 'bar bar)) instead of having to do > (select-dao 'foo (:= 'bar (id bar))) And the second allows the use of a DAO-CLASS name in the :COL-TYPE field of a slot definition. EG: > (defclass bar () ((id :col-type serial)) (:metaclass dao-class)) > (defclass foo () ((bar :col-type (or db-null bar))) (:metaclass dao-class)) instead of > (defclass bar () ((id :col-type serial)) (:metaclass dao-class)) > (defclass foo () ((bar :col-type (or db-null integer))) (:metaclass dao-class)) These both seem pretty basic, but they mean that you can change the primary key column name or type without having to make changes throughout your code. Also, I see it as a first step toward being able to (eagerly or lazily) auto-populate slots with full objects rather than keys. Does this seem useful, too magical, or already there but I missed it?

2 1

[postmodern-devel] Postmodern and Windows
by Daniel Brunner 14 Mar '12

14 Mar '12

Hello, I have flipped through the mailing list's archive but did not find a solution: Is Postmodern known to run under Windows? I have several PCs with Windows (XP and 7) where I use Clozure CL but Postmodern is not working. My setup: - Windows XP or Windows 7 (32 Bit) - The database is local (9.1.3) or via the network (8.4). - I use the newest Postmodern via the March distribution of Quicklisp - I user Clozure CL version 1.7 I can do a CONNECT-TOPLEVEL and with the pgadmin3 tool I can see the connection. But after a simple query like (QUERY "select 10") I get an error: --8<-- Database error: on #<BASIC-TCP-STREAM: CLOSED #xCB1E1BE>: Das Geraet erkennt den Befehl nicht. (error #22) during write [Condition of type CL-POSTGRES:DATABASE-SOCKE-ERROR --8<-- The "Das Geraet erkennt den Befehl nicht" would be something like "The device doesn't recognise the command." in English. I do not have the original error message at hand. In the PostgreSQL-Log I see the message "ungueltige Message-Laenge". That would be something like "invalid message length". Am I doing something wrong? Wrong configuration? Encoding issue? I have no idea how to fix that problem. Kind regards, Daniel.

3 4

[postmodern-devel] Regression in handling integer dates and timestamps
by Lucas Hope 14 Feb '12

14 Feb '12

Hi there, The following code sample used to work on postmodern-20110219-git (using quicklisp from that period). However it now breaks. I can no longer insert integers as dates or timestamps into tables. Updates don't work either, but the example below uses insert: (ql:quickload "postmodern") ;; quicklisp version released yesterday - postmodern-20111203-git (pomo:connect-toplevel "date_test" "snip" "snip" "localhost") (gethash "integer_datetimes" (pomo::connection-parameters pomo:*database*)) => "on" => T (pomo:execute "create table date ( value date );") (pomo:execute "insert into date ( value ) values ( $1 )" "2010-01-01") (setf date (pomo:query "select * from date limit 1" :single)) => 3471292800 (ignore-errors (pomo:execute "insert into date ( value ) values ( $1 )" date)) => NIL => #<CL-POSTGRES-ERROR:INVALID-DATETIME-FORMAT {1004A00391}> (pomo:execute "create table timestamp ( value timestamp );") (pomo:execute "insert into timestamp ( value ) values ( $1 )" "2010-01-01") 1 1 (setf timestamp (pomo:query "select * from timestamp limit 1" :single)) => 3471292800 (ignore-errors (pomo:execute "insert into timestamp ( value ) values ( $1 )" timestamp)) => NIL => #<CL-POSTGRES-ERROR:INVALID-DATETIME-FORMAT {100403F391}> -- --------------------------------------------------- Dr Lucas Hope - lucas.r.hope@skype Machine Learning and Software Engineering Consultant Melbourne, Australia

2 4

[postmodern-devel] "WHERE id IN (1, 2, 3)" conditions
by Nicolas Martyanoff 28 Dec '11

28 Dec '11

Hi, I'm trying to use queries such as: SELECT a, b, c FROM foo WHERE id IN (1, 2, 3) While it's possible to nest queries with IN: (:select 'a 'b 'c :from 'foo :where (:in 'id (:select 'd :from 'bar))) It's not possible to have: (:select 'a 'b 'c :from 'foo :where (:in 'id (list 1 2 3)) => Value (1 2 3) can not be converted to an SQL literal. Would you be ok with lists being converted to (a, b, ...) SQL literals ? Regards, -- Nicolas Martyanoff http://codemore.org khaelin(a)gmail.com

2 2

[postmodern-devel] OSX 10.6.8 Intel - SBCL 1.0.54 The function cl-postgres::write-uint4 is undefined.
by Carr Colin 20 Dec '11

20 Dec '11

Hi, having some difficulty with OSX 10.6.8 Intel - SBCL 1.0.54 I used quicklisp (most current) to install and my debian (6.0.3) boxes are fine but my Macbook Pro (10.6.8) is having the issue. The same error is happening when I use; postgresql 8.4 or 9.1 locally (running on OSX) or remote to a debian box running 8.4 and even a VM (VirtualBox) running debian (6.0.3) on the Mac with NAT forwarding to postgres 8.4. I can connect with psql in the various configurations described for the remote connection I made the appropriate "all/all/trusted" additions to the "/etc/" files so it is unencumbered by any security. I deleted my FASLs and I tried connecting without a database running and the FASL removal and "re-load" did not solve the issue and the connect-toplevel without a database running error was what I expected. The Postgres is a "clean" install with only the ytestdb added on all systems I tested against. ytestdb is the database postgres is the user post is the password ;;ERROR cl-postgre::write-uint4 undefined (messages.lisp) I hope this information is helpful. Thanks, - C cl-user> (asdf:oos 'asdf:load-op :postmodern) #<asdf:load-op nil {1003053F83}> nil cl-user> (use-package :postmodern) t cl-user> (connect-toplevel "ytestdb" "postgres" "post" "localhost") ; Evaluation aborted on #<cl-postgres:database-socket-error {100874D7A3}>. ;;; THIS IS WITH NO POSTGRES RUNNING cl-user> (connect-toplevel "ytestdb" "postgres" "post" "localhost") The function cl-postgres::write-uint4 is undefined. [Condition of type undefined-function] Restarts: 0: [retry] Retry SLIME REPL evaluation request. 1: [*abort] Return to SLIME's top level. 2: [terminate-thread] Terminate this thread (#<thread "repl-thread" running {1002BE0043}>) Backtrace: 0: ("bogus stack frame") [No Locals] 1: (cl-postgres::startup-message #<unavailable argument> #<unavailable argument> #<unavailable argument>) Locals: sb-debug::arg-0 = :<not-available> sb-debug::arg-1 = :<not-available> sb-debug::arg-2 = :<not-available> 2: (cl-postgres::authenticate #<unavailable argument> "postgres" "post" "ytestdb" :no) Locals: sb-debug::arg-0 = :<not-available> sb-debug::arg-1 = "postgres" sb-debug::arg-2 = "post" sb-debug::arg-3 = "ytestdb" sb-debug::arg-4 = :no 3: (cl-postgres::initiate-connection #<database-connection {10089CD923}>) Locals: sb-debug::arg-0 = #<database-connection {10089CD923}> 4: (cl-postgres:open-database #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument> #<unavailable argument>) Locals: cl-postgres::database = :<not-available> cl-postgres::host = :<not-available> cl-postgres::password = :<not-available> cl-postgres::port = :<not-available> cl-postgres::use-ssl = :<not-available> cl-postgres::user = :<not-available> 5: (connect-toplevel "ytestdb" "postgres" "post" "localhost" :port 5432 :use-ssl nil) Locals: postmodern::database = "ytestdb" postmodern::host = "localhost" #:n-supplied-32 = nil postmodern::password = "post" postmodern::user = "postgres" #:|port-DEFAULTING-TEMP| = 5432 #:|use-ssl-DEFAULTING-TEMP| = nil 6: (sb-int:simple-eval-in-lexenv (connect-toplevel "ytestdb" "postgres" "post" "localhost") #<NULL-LEXENV>) Locals: sb-debug::arg-0 = (connect-toplevel "ytestdb" "postgres" "post" "localhost") sb-debug::arg-1 = #<NULL-LEXENV> 7: (eval (connect-toplevel "ytestdb" "postgres" "post" "localhost")) Locals: sb-debug::arg-0 = (connect-toplevel "ytestdb" "postgres" "post" "localhost") 8: (swank::eval-region "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\")\n") Locals: sb-debug::arg-0 = "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\")\n" 9: ((lambda () :in swank::repl-eval)) [No Locals] 10: (swank::track-package #<CLOSURE (lambda # :in swank::repl-eval) {10089CD43B}>) Locals: sb-debug::arg-0 = #<CLOSURE (lambda () :in swank::repl-eval) {10089CD43B}> 11: (swank::call-with-retry-restart "Retry SLIME REPL evaluation request." #<CLOSURE (lambda # :in swank::repl-eval) {10089CD35B}>) Locals: sb-debug::arg-0 = "Retry SLIME REPL evaluation request." sb-debug::arg-1 = #<CLOSURE (lambda () :in swank::repl-eval) {10089CD35B}> 12: (swank::call-with-buffer-syntax nil #<CLOSURE (lambda # :in swank::repl-eval) {10089CD32B}>) Locals: sb-debug::arg-0 = nil sb-debug::arg-1 = #<CLOSURE (lambda () :in swank::repl-eval) {10089CD32B}> 13: (swank::repl-eval "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\")\n") Locals: sb-debug::arg-0 = "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\")\n" 14: (sb-int:simple-eval-in-lexenv (swank:listener-eval "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\") ..) Locals: sb-debug::arg-0 = (swank:listener-eval ..) sb-debug::arg-1 = #<NULL-LEXENV> 15: (eval (swank:listener-eval "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\") ..) Locals: sb-debug::arg-0 = (swank:listener-eval ..) 16: (swank:eval-for-emacs (swank:listener-eval "(connect-toplevel \"ytestdb\" \"postgres\" \"post\" \"localhost\")\n") "COMMON-LISP-USER" 40) Locals: sb-debug::arg-0 = (swank:listener-eval ..) sb-debug::arg-1 = "COMMON-LISP-USER" sb-debug::arg-2 = 40 17: (swank::process-requests nil) Locals: sb-debug::arg-0 = nil 18: ((lambda () :in swank::handle-requests)) 19: ((lambda () :in swank::handle-requests)) 20: (swank-backend::call-with-break-hook #<FUNCTION swank:swank-debugger-hook> #<CLOSURE (lambda # :in swank::handle-requests) {1002BF011B}>) 21: ((flet swank-backend:call-with-debugger-hook :in "/Users/cpc26/quicklisp/dists/quicklisp/software/slime-20111105-cvs/swank-sbcl.lisp") ..) 22: (swank::call-with-bindings ..) 23: (swank::handle-requests #<swank::connection {1003DA2BF3}> nil) 24: ((flet #:without-interrupts-body-243284 :in sb-thread:make-thread)) 25: ((flet sb-thread::with-mutex-thunk :in sb-thread:make-thread)) 26: ((flet #:without-interrupts-body-88835 :in sb-thread::call-with-mutex)) 27: (sb-thread::call-with-mutex ..) 28: (sb-thread::initial-thread-function) 29: ("foreign function: call_into_lisp") 30: ("foreign function: new_thread_trampoline") 31: ("foreign function: _pthread_start") 32: ("foreign function: thread_start")

2 1

[postmodern-devel] Patch: Make :|| (symbol with an empty name) equivalent to :\|\|
by Stas Boukarev 21 Nov '11

21 Nov '11

:|| is a valid symbol in CL, its name is an empty string, "", and it would be much more pleasant to use it for concatenation instead of :\|\|. The attached patch adds :|| operator. -- With best regards, Stas.

3 5

[postmodern-devel] <> operator
by Zach Beane 18 Nov '11

18 Nov '11

Out of SQL habit I used <> for inequality yesterday and got this error: function __(integer, integer) does not exist Should I just stick with !=? Zach

3 2

[postmodern-devel] cl-postgres fails to read an empty array
by Andy Chambers 03 Nov '11

03 Nov '11

Hi, I'm not sure if this is the case in the latest version of postgresql but in my version, it fails to read an empty integer correctly from the DB. The following patch fixes for me... diff --git Postmodern/cl-postgres/interpret.lisp Postmodern/cl-postgres/\ interpret.lisp index 7d30f75..a6ce46f 100644 --- Postmodern/cl-postgres/interpret.lisp +++ Postmodern/cl-postgres/interpret.lisp @@ -196,8 +196,13 @@ used. Correct for sign bit when using integer format." (unless (< (incf pos) (length value)) (return ws))) 'simple-vector))))) +(defun maybe-parse-integer (s) + (if (string= "" s) + :null + (parse-integer s))) + ;; Integral array types -(let ((read-integral (read-array-value #'parse-integer))) +(let ((read-integral (read-array-value #'maybe-parse-integer))) (dolist (oid '(1561 1005 1007 1016 1028)) (set-sql-reader oid read-integral))) Cheers, Andy

2 1

[postmodern-devel] Release 1.18
by Marijn Haverbeke 19 Oct '11

19 Oct '11

I just tagged the current version as release 1.18. See the project page [1] for a summary of changes. [1]: http://marijnhaverbeke.nl/postmodern

1 0

[postmodern-devel] setting default value for serial column in prepared insert statement execution
by Antony 05 Sep '11

05 Sep '11

Hi I was trying to find how to use the 'serial' (auto increment) type through cl-postgres prepared insert statement execution. According to http://www.postgresql.org/docs/9.0/interactive/datatype-numeric.html#DATATY… I basically have two choices for defaulting a serial column value 1. pass the DEFAULT keyword for the column value 2. do not include the serial column in the insert statement The way my code is setup, it's more convoluted to do #2 I wanted to check if it's possible to do #1. That would really make a big difference to me. -Antony

4 5

[postmodern-devel] cl-postgress build warning due to multiple loading
by Antony 13 Aug '11

13 Aug '11

Hi I am beginning to use cl-postgress part of postmodern It is working well, Thank you. I have an issue that would be nice to fix. When I do (asdf:oos 'asdf:load-op :cl-postgres) I see couple of warnings like ;Compiler warnings for "/media/sf_git/thirdparty/postmodern/simple-date/cl-postgres-glue.lisp" : ; In an anonymous lambda form at position 857: Duplicate definitions of (:METHOD CL-POSTGRES:TO-SQL-STRING (DATE)), in this file and in "/media/sf_git/thirdparty/postmodern/simple-date/cl-postgres-glue.lisp" I think they are due to in file cl-postgress.asd at the end you have (asdf:oos 'asdf:load-op :simple-date-postgres-glue) and again in simple-date.asd you have the same line (asdf:oos 'asdf:load-op :simple-date-postgres-glue) Can this be fixed. I am using CCL Clozure Common Lisp Version 1.7-dev-r14812M-trunk (LinuxX8664)! My ASDF is a bit old (2.011.9), asdf is one hting I don't like upgrading, causes me a lot of pain. -Antony

3 6