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

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