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

[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