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

Re: [postmodern-devel] Patch for with-column-writers?
by Curtis Schlak 27 Oct '09

27 Oct '09

Marijn, Brilliant! Thank you for the fix. I enjoy your libraries and, if I find something else that can help, I'll be sure to send the email. Skaal! Curtis.

1 0

[postmodern-devel] Patch for with-column-writers?
by Curtis Schlak 27 Oct '09

27 Oct '09

I tried multiple ways to get the with-column-writers macro in the repository to work and could not. I believe that the loop should read :in rather than :on as follows: (defmacro with-column-writers ((&rest defs) &body body) `(let ((*custom-column-writers* (append (list ,@(loop :for (field writer) :in defs :collect `(cons (to-sql-name ,field) ,writer))) *custom-column-writers*))) ,@body)) With that in place, the following code works correctly: (defclass foo () ((id :col-type int :initform :id :accessor foo-id) (stuff :initform :stuff :accessor foo-stuff)) (:metaclass postmodern:dao-class) (:keys id)) (setf foo (postmodern:with-column-writers ((:id #'(lambda (inst val) (setf (foo-id inst) val) (setf (foo-stuff inst) (format nil "My Value: ~A" val))))) (postmodern:get-dao 'foo 1)))

2 1

[postmodern-devel] Error when using :col-type serial
by Mitch Berkson 19 Oct '09

19 Oct '09

I defined a dao class which I would like to get a sequential id from the database. For the id slot I have: (id :col-type serial :accessor seat-id) When I try to do an update-dao with an instance of that class, I get: Error: The slot ID is unbound in the object #<CPA-SEAT 2665E40F> (an instance of class #<DAO-CLASS CPA-SEAT 25EE423B>). I'd appreciate any suggestions about what I'm doing wrong. Thank you. Mitch

2 2

[postmodern-devel] simple-date:date and "can not be converted to an SQL literal." error
by Mikhail Shevchuk 18 Oct '09

18 Oct '09

Hello, forum! I have a dao class that uses 'date' col-type: (reg_date :col-type date :initarg :date :accessor user-reg-date :initform (get-current-simple-date))) here is a (get-current-simple-date) result: #<SIMPLE-DATE:DATE 17-10-2009> but the following error is generated when I'm trying to instantiate the object: Value #<SIMPLE-DATE:DATE 17-10-2009> can not be converted to an SQL literal. [Condition of type SIMPLE-ERROR] Thanks in advance! -- http://blog.shevchuk.org

2 7

[postmodern-devel] Multiple values from row-readers
by Russ Tyndall 07 Oct '09

07 Oct '09

I was wondering if it was a bug or intended behavior that row reader functions do not properly return multiple values? I am working on a cl-postgres backend to clsql, so I am not very familiar with much of the workings of this project, but noticed this somewhat odd (from my perspective) behavior. I have worked around this in the obvious way (list instead of multiple values). It seems to be a problem with the returning-effected-rows macro (which expands to a let, effectively discarding any multiple values returned from the row reader). Is there a reason not to change the definition to the following? http://paste.lisp.org/display/88358 Cheers, Russ Tyndall

2 1

Re: [postmodern-devel] [Sbcl-devel] Possible bug in REFILL-INPUT-BUFFER
by Attila Lendvai 06 Oct '09

06 Oct '09

> 3: (SB-UNIX::NOTE-DANGEROUS-SELECT) > 4: (SB-IMPL::SUB-SUB-SERVE-EVENT NIL NIL) > 5: (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL) > 6: (SB-SYS:WAIT-UNTIL-FD-USABLE 13 :INPUT NIL) > 7: (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "a socket" {100338FE81}>) > 8: (SB-IMPL::INPUT-UNSIGNED-8BIT-BYTE #<SB-SYS:FD-STREAM for "a socket" {100338FE81}> T NIL) > 9: (CL-POSTGRES::READ-UINT1 #<unavailable argument>) fyi, we have a postmodern branch which has a patch to make it use iolib as the socket backend. we also had some issues with sb-bsd-sockets before... i CC the postmodern list to give another data point why it's a good idea to have iolib as the socket backend. http://dwim.hu/darcsweb/darcsweb.cgi?r=HEAD%20postmodern;a=summary or darcs pull http://dwim.hu/darcs/postmodern/ hth, -- attila

3 8

[postmodern-devel] Anyone tried to use the new recursive with in Postgresql 8.4 with S-SQL?
by Sabra Crolleton 05 Oct '09

05 Oct '09

I can't seem to get the syntax right using s-sql. I can write a straight sql statement, but it looks ugly in the middle of a lisp program. Sample sql statement from the postgresql docs is: WITH RECURSIVE search_graph(id, link, data, depth, path, cycle) AS ( SELECT g.id, g.link, g.data, 1, ARRAY[g.id], false FROM graph g UNION ALL SELECT g.id, g.link, g.data, sg.depth + 1, path || g.id, g.id = ANY(path) FROM graph g, search_graph sg WHERE g.id = sg.link AND NOT cycle ) SELECT * FROM search_graph; http://www.postgresql.org/docs/8.4/static/queries-with.html Sabra

2 1

[postmodern-devel] Using simple-date date class as :col-type
by Mitch Berkson 25 Sep '09

25 Sep '09

I have not been successful using the date class as a :col-type in a DAO. Here is what I have tried: (defclass cpa-address () ((id :col-type integer :accessor address-id) (start_date :col-type date :accessor address-start-date) (version :col-type integer)) (:metaclass postmodern:dao-class) (:keys id) (:table-name gt_address)) In the Postgres database, the field type of start_date is date. When I select a cpa-address DAO, I expect to see a symbol of type simple-date in the start_date slot, but what I get is a CL universal time. Should I be trying something else to take advantage of simple-date? Thanks for any help. Mitch

2 2

[postmodern-devel] "defined more than once in table.lisp" warnings
by Mitch Berkson 24 Sep '09

24 Sep '09

When I run a select-dao, the REPL prints a bunch of warnings like: Warning: (METHOD UPDATE-DAO (CPA-SERIES)) defined more than once in d:\lisp\postmodern\postmodern\table.lisp. Is this something I can fix? Thanks for any help. Mitch

2 5

[postmodern-devel] Error if SSL and no client cert and key files specified
by Mitch Berkson 05 Sep '09

05 Sep '09

If I call make-ssl-stream with *ssl-key-file* and *ssl-certificate-file* both nil, I get the following error: Error: A failure in the SSL library occurred on handle #<Pointer to type :VOID = #x02600208>. (Return code: 1)SSL error queue: error:140C5042:SSL routines:SSL_UNDEFINED_FUNCTION:called a function you should not call Does this mean that it's not possible to make a unilateral SSL connection? Should there be a more user-friendly error message? Thanks for any help. Mitch

2 3

[postmodern-devel] darcs patch: add support for the currval() and lastval() functions
by khaelin＠gmail.com 31 Aug '09

31 Aug '09

Sun Aug 30 19:25:12 CEST 2009 khaelin(a)gmail.com * add support for the currval() and lastval() functions

3 5

[postmodern-devel] Large objects support
by Nicolas Martyanoff 30 Aug '09

30 Aug '09

Hi, Is there a large object¹ support in development, or do you intend to add one in the future? 1. http://www.postgresql.org/docs/8.4/static/largeobjects.html Regards, -- Nicolas Martyanoff http://codemore.org khaelin(a)gmail.com

2 2

[postmodern-devel] Wildacrds in string patterns
by Sebastian Tennant 29 Aug '09

29 Aug '09

Hi all, What's the trick for using wildcards such as '%' in string patterns in queries? I can't find anything on it in the S-SQL reference and I've tried several different things - I either get a database error or the Emacs debugger kicks in complaining about an end of file, or some such problem. Regards, Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap

2 2

[postmodern-devel] Using get-dao to somehow pull in foreign key linked fields?
by Sabra Crolleton 28 Aug '09

28 Aug '09

I was just going to display the fields in a record and my first thought was to use the relevant class and then just call get-dao and iterate over the slots, something like: (item (postmodern:get-dao 'countrynotes (parse-integer id)))) However, looking at the countrynotes definition, you quickly notice that it has a foreign key: ; shortened version of the countrynotes class (defclass countrynotes () ( (id :accessor id :col-type int4 :initarg :id ) (country-id :accessor country-id :col-type int4 :initarg :country-id :foreign-key (countries id)) (name :accessor name :col-type varchar :initarg :name ) (updated-at :accessor updated-at :col-type timestamp :initarg :updated-at )) (:metaclass postmodern:dao-class) (:table-name countrynotes)(:keys id)) In displaying the countrynote, I don't really want to show the country-id, I really want to display the name of the country instead, which is another table: (defclass countries () ( (id :accessor id :col-type int4 :initarg :id ) (name :accessor name :col-type varchar :initarg :name ) (updated-at :accessor updated-at :col-type timestamp :initarg :updated-at )) (:metaclass postmodern:dao-class) (:table-name countries)(:keys id)) I can easily write out the full required sql statement, but is there a simple way of just using the dao? Sabra

2 1

[postmodern-devel] Authentication
by Sebastian Tennant 27 Aug '09

27 Aug '09

Hi all, It seems it is not possible to connect to a local postgres server using the 'ident sameuser' authentication method - the two functions 'connect' and 'connect-toplevel' both require user and password arguments. I thought perhaps passing empty strings as user and password arguments might be the way to say "use the ident sameuser method" but alas, it raises the error: "Database error 28000: no PostgreSQL user name specified in startup packet" Perhaps this is a feature that is lacking, or am I missing something? Regards, Sebastian P.S. Apologies if this is a FAQ. A Gmane search of this list for 'ident sameuser' returned no results. -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap

3 2

[postmodern-devel] Add :add-column action to :alter-table
by Daniel White 25 Aug '09

25 Aug '09

Patch attached adds an :add-column action to :alter-table where the column should be the same form as a column in :create-table. For example: (:alter-table table :add-column col-name :type string :default "default")) -- Daniel White

2 1

[postmodern-devel] [S-SQL] Multiple rows in INSERT INTO clause
by Timur Sufiev 25 Aug '09

25 Aug '09

Is there some way in S-SQL to generate INSERT INTO clauses with multiple rows, e.g. "INSERT INTO \"table\" (a, b) VALUES (10, 20), (30, 40)" ? Desired sexp format is `(:insert-into table :set a (10 20) b (30 40)), transformation can work like a MAPCAR: stop processing values sequences as soon as the end of the shortest one is reached. The reason to have such a feature is a performance issue: having a sequence of rows to be inserted we want to minimize the overhead related with sending queries to db; one query inserting, say, 50 rows is certainly faster than 50 queries each inserting 1 row. I would prepare the patch myself, but the syntax of s-sql.lisp is a bit too tricky for me :(. -- Timur Sufiev -- Timur Sufiev

2 2

[postmodern-devel] s-sql: delete cascade
by Nicolas Martyanoff 04 Jul '09

04 Jul '09

Hi, I can't find a way to express a "DELETE table CASCADE" with s-sql. How can I do this ? Regards, -- Nicolas Martyanoff http://codemore.org khaelin(a)gmail.com

2 1

[postmodern-devel] IF-EXISTS operator for DROP-* ops
by Daniel White 28 May '09

28 May '09

I'm wanting to use the IF EXISTS modifier for the various DROP operations, and it seems like the semantics of CASCADE works best for this case. The following is a proof of concept implementation. If there aren't any issues or complaints I'll write a patch that covers the rest of the DROP operations. (defvar *expand-if-exists* nil) (defun expand-if-exists () (when *expand-if-exists* `("IF EXISTS "))) (def-sql-op :if-exists (op) (let ((*expand-if-exists* t)) (sql-expand op))) (def-sql-op :drop-sequence (name) `("DROP SEQUENCE " ,@(expand-if-exists) ,@(sql-expand name))) (sql (:if-exists (:drop-sequence 'sequence))) Cheers, -- Daniel White

2 1

[postmodern-devel] with-connection is strange...
by Lucas Hope 26 May '09

26 May '09

Hi there, The macro with-connection doesn't seem to work as I would expect. It seems two macros were merged... I am curious as to why the following definition is used: (defmacro with-connection (spec &body body) "Like with-connection, but evaluate the specification list." `(let ((*database* (apply #'connect ,spec))) (unwind-protect (progn ,@body) (disconnect *database*)))) Note the documentation above. I think a more standard "with-" macro doesn't evaluate the spec (like below). (defmacro with-connection (spec &body body) "Like with-connection, but evaluate the specification list." `(let ((*database* (connect ,@spec))) (unwind-protect (progn ,@body) (disconnect *database*)))) What's the reasoning here? -Luke

2 1

[postmodern-devel] s-sql: Better join keyword recognition
by Andreas Fuchs 09 Apr '09

09 Apr '09

Hi there, I'd really like to use the NATURAL <x> JOIN facility in postgresql as outlined in http://www.postgresql.org/docs/8.3/interactive/queries-table-expressions.ht…, so my first instinct was to patch s-sql (-: This patch also fixes the syntax emitted for :cross-join (it really doesn't require an :ON) and adds a :USING keyword to specify the same-named columns to use for joining. The result can be used like so: (:select 'x 'y :from 'foo :cross-join 'bar) (:select 'x 'y :from 'foo :natural-left-join 'bar :where (:= 'a 2)) (:select 'x 'y :from 'foo :natural-inner-join 'bar :where (:= 'a 1)) (:select 'x 'y :from 'foo :outer-join 'bar :using ('a 'b 'c)) ;;; which is mostly equivalent to: (:select 'x 'y :from 'foo :inner-join 'bar :on (:and (:= 'foo.a 'bar.a) (:= 'foo.b 'bar.b) (:= 'foo.c 'bar.c))) I hope you find the attached patch useful, and will consider committing it. Cheers, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

2 2

None
by Lucas Hope 16 Mar '09

16 Mar '09

1 0

[postmodern-devel] Bug when redefining a class.
by Lucas Hope 11 Mar '09

11 Mar '09

Hi again, The following triggers an incorrect error for me. Not a major bug since the third case provides a workaround. (defclass FOO () ((bar :col-type real)) (:metaclass dao-class) (:keys baz)) (dao-table-definition 'foo) ;; correct error. ;; redefine: (defclass FOO () ((bar :col-type real)) (:metaclass dao-class)) ;; incorrect error! ;; redefine: (defclass FOO () ((bar :col-type real)) (:metaclass dao-class) (:keys bar)) ;; works, then can run the second defclass successfully. -Luke

2 1

[postmodern-devel] Can't redefine slots as columns - why?
by Lucas Hope 10 Mar '09

10 Mar '09

Hi there, I am just getting my feet wet with postmodern. It looks like I will be doing some heavy development with it for the next couple of weeks. Wish me luck! My (first?) issue is that I want to do something similar to the following example code. Here CIRCLE is an in-memory implementation of a circle, and it is desired to create a DAO object which moves storage to a postgres backend. (We have lots of circles...) Pretend CIRCLE has a host of useful functionality attached and I can't just point all the defmethods to DAO-CIRCLE. (defclass SHAPE () ()) (defclass CIRCLE (SHAPE) (radius)) (defclass DAO-CIRCLE (CIRCLE) ((radius :col-type real)) (:metaclass dao-class)) (dao-table-definition 'dao-circle) => ERROR: Slot RADIUS in class #<DAO-CLASS DAO-CIRCLE> is both a column slot and a regular slot. Why doesn't this work, and how can I make it work? It seems like this is useful functionality to have. I want the DAO-CIRCLE's radius to be a column slot. Cheers, -Luke

2 6

[postmodern-devel] Release 1.14
by Marijn Haverbeke 08 Mar '09

08 Mar '09

I've released 1.14. No major changes, but there was some small stuff sitting in the repo, and the half-year-old date of the last release made the project page look a bit dead ;). http://common-lisp.net/project/postmodern/postmodern-1.14.tgz Best, Marijn

3 4