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

[postmodern-devel] Dash in Postgresql Column name - "query-dao"
by Phil 03 Dec '08

03 Dec '08

query-dao does not seem to like column names with a dash in them like column-name and I suspect it would have the same problem with spaces. I know that the preffered for postgresql would be column_name but I though that being able to use the dash would simplify going from db to dao object to html and back, well at least for me. Is column names with dashes just not supported, a bug or on the wish list? Thanx

4 7

[postmodern-devel] [patch] export postmodern:dao-keys
by Maciej Pasternacki 25 Nov '08

25 Nov '08

Hello, I just written a simple DAO cache for my app (for curious: http://paste.lisp.org/display/70998 - I wrap Hunchentoot request handler body with WITH-DAO-CACHE and it caches DAO of given class and primary key to avoid repeated SELECTs when serving a single request). For the caching to work well, I need to figure out keys of a DAO, and this functionality is unexported. Attached patch exports (and documents) DAO-KEYS, adds method for a symbol (invoking DAO-KEYS on class named by a symbol), and for a DAO instance (returning list of values that are instance's primary key). Regards, Maciej -- Maciej Pasternacki -><- http://www.pasternacki.net/ -><- http://www.3ofcoins.net/

2 1

[postmodern-devel] Clozure CL Unicode support
by Daniel Lyons 24 Nov '08

24 Nov '08

Hi, I have a trivial change request, which I am currently hacking around. Currently, cl-postgres.asd contains: (defparameter *unicode* #+(or sb-unicode unicode ics) t #-(or sb-unicode unicode ics) nil) It would make life slightly easier and less confusing for Clozure users if this could be extended just slightly: (defparameter *unicode* #+(or sb-unicode unicode ics ccl) t #-(or sb-unicode unicode ics ccl) nil) Clozure supposedly only uses Unicode for characters, so it ought to be a fine assumption. I've gotten around this on a current project by placing these lines in my .asd file: #+ccl (push :unicode *features*) The *features* variable seems to also include some other options if you'd rather (I don't know if any of these are deprecated or preferable, I'm a bit new to all this): :clozure, :clozure-common- lisp, :openmcl-unicode-strings. Oh, and incidentally, thanks for this library! I haven't been so pleased with a database library for as long as I can remember. It's really a joy to use. — Daniel Lyons http://www.storytotell.org -- Tell It!

2 1

[postmodern-devel] Multirow inserts and transactions in postmodern
by Harry Bock 12 Nov '08

12 Nov '08

Hi, I'm wonder what the proper :insert-into syntax would be to insert multiple rows simultaneously, like so: "INSERT INTO my_table (col1, col2, col3) VALUES ('1', '2', '3'), ('4', '5', '6'), ...;" As this tends to be much faster when inserting large data sets. Also, the transaction functionality of postmodern doesn't seem to be well-documented. Is the only method of working with them to wrap calls in the with-transaction macro? Thanks, Harry -- Harry Bock Software Developer, Package Maintainer OSHEAN, Inc. Email: harry(a)oshean.org PGP Key ID: 546CC353

2 3

[postmodern-devel] select distinct
by Jens Teich 02 Nov '08

02 Nov '08

How do I express a SELECT statement in s-sql using DISTINCT to receive only unique values? Jens

2 2

[postmodern-devel] Incorrect :cast compilation
by Yuri Vishnevsky 28 Oct '08

28 Oct '08

Hi. I've upgraded from postmodern-0.24 to 1.13 recently and noticed that :cast is incorectly escaped in sql expressions. (sql-compile '(:cast (:as value :BIGINT))) produces \"cast\"(value AS bigint) which results in postgres error. Removing "cast" from s-sql::*postgres-reserved-words* seems to fix the things.

2 2

[postmodern-devel] [patch] ALTER TABLE, named constraints, typos
by Maciej Pasternacki 22 Oct '08

22 Oct '08

Hello, I attach: support for ALTER TABLE statement (initial, only defining constraints) and named table constraints in s-sql, and fix for a typo in documentation and for a compiler warning I found on my way. Regards, Maciej -- -><- Maciej Pasternacki -><- http://www.pasternacki.net/ -><-

2 3

[postmodern-devel] (:nextval a-symbol)
by Lars Rune Nøstdal 22 Oct '08

22 Oct '08

took me a while to figure out that only strings are supported for :nextval in a :col-default context, so: lnostdal@blackbox:~/programming/lisp/postmodern/postmodern$ darcs diff -u diff -rN -u old-postmodern/postmodern/table.lisp new-postmodern/postmodern/table.lisp --- old-postmodern/postmodern/table.lisp 2008-10-13 14:11:29.000000000 +0200 +++ new-postmodern/postmodern/table.lisp 2008-10-13 14:11:29.000000000 +0200 @@ -293,6 +293,10 @@ ,(loop :for slot :in (dao-column-slots table) :collect `(,(slot-definition-name slot) :type ,(column-type slot) ,@(when (slot-boundp slot 'col-default) - `(:default ,(column-default slot))))) + `(:default ,(let ((col-def (column-default slot))) + (when (eq :nextval (first col-def)) + (setf (second col-def) + (to-identifier (second col-def)))) + col-def))))) ,@(when (dao-keys table) `((:primary-key ,@(dao-keys table))))))) ..then.. (defclass user () ((id :col-type integer :reader id-of :col-default (:nextval user-id-seq)) ...)) ..i don't know. -- Lars Rune Nøstdal || AJAX/Comet GUI type stuff for Common Lisp http://nostdal.org/ || http://groups.google.com/group/symbolicweb

2 3

[postmodern-devel] patch: DAO constraints
by Maciej Pasternacki 14 Oct '08

14 Oct '08

Hello, Since it's not my first patch for Postmodern, and most probably not the last one, I can as well subscribe to the list and send patches properly instead of in a private e-mail. I just made a small update to DAOs to use constraints (foreign keys, checks, indices) for DAO slots and classes. Doesn't seem to break anything, and makes it possible (or almost possible) to drop separate .sql definition files and just use DAO-TABLE-DEFINITION. What's missing for me is arbitrary SQL for e.g. defining needed functions, enum types and so on before creating table -- but I'm not sure what approach should I take: move it all to DAOs (as e.g. :BEFORE- CREATE-TABLE and :AFTER-CREATE-TABLE class slots), or just make init function for my package, which would call needed queries and use DAO- TABLE-DEFINITION just to create the tables. Would there be any advantage to :BEFORE-... and :AFTER-... slots, or is the init function the preferred way to go? Regards, Maciej. -- -><- Maciej Pasternacki -><- http://www.pasternacki.net/ -><-

2 5

[postmodern-devel] doquery - iterating rows
by Mark Slamin 01 Oct '08

01 Oct '08

Sorry, more questions. I'm trying to iterate down rows in the database. Using doquery like this: (defun iterate-rows () (doquery (query (:select 'name :from 'htable) :list) (xname) (print xname))) I receive the following error: The value of CL-POSTGRES::QUERY is ("(A B)"), which is not of type STRING. [Condition of type SIMPLE-TYPE-ERROR] I'm not sure what to do with that. Also, on a broader scale, what I'm trying to do is iterate through the rows of a large database and I don't want to load the entire results of the query into memory. Ideally I just want to load one record with all its fields, perform some operations on that data, write the record back if its been updated, and then move to the next record. Is doquery the best method for that? Or is there something else that would work better? Thank you, Mark

2 1