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

Re: [postmodern-devel] Get keys out of dao-class
by Phil Marneweck 27 Feb '09

27 Feb '09

Ok I figured it out, dao-keys "method" is a reader for effective-keys on dao-class. I am still learning clos... *sigh* On Fri, 2009-02-27 at 11:24 +0200, Phil Marneweck wrote: > Thanx, I never thought about it being a method. I don't know how I > missed it looking at the code. It works fine but I would like to > understand how it works... > > If I understand correctly there is two versions, the first returns a > list of keys and the second returns a list of key values. > > ;;first > (defmethod dao-keys ((class-name symbol)) > (dao-keys (find-class class-name))) > > ;;second > (defmethod dao-keys (dao) > (mapcar #'(lambda (slot) > (slot-value dao slot)) > (dao-keys (class-of dao)))) > > Please explain to me how the first one works, to me it just looks like > it calls itself? > > Thanx > > > > ----- Original Message ------ > From:Marijn Haverbeke > Sent:Friday, February 27, 2009 09:37 > To: postmodern-devel(a)common-lisp.net; > Subject:Re: [postmodern-devel] Get keys out of dao-class > > > Doesn't dao-keys work? There's no defun for it since it's a method. > Call it on a class to get the slot names, on an instance to get the > slot values. > > Best, > Marijn > > _______________________________________________ > postmodern-devel mailing list > postmodern-devel(a)common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel > > >

1 0

Re: [postmodern-devel] Get keys out of dao-class
by Phil Marneweck 27 Feb '09

27 Feb '09

Thanx, I never thought about it being a method. I have not tried it yet, I was interested in seeing how it works, that is why I was scratching in the code. ----- Original Message ------ From:Marijn Haverbeke Sent:Friday, February 27, 2009 09:37 To: postmodern-devel(a)common-lisp.net; Subject:Re: [postmodern-devel] Get keys out of dao-class Doesn't dao-keys work? There's no defun for it since it's a method. Call it on a class to get the slot names, on an instance to get the slot values. Best, Marijn _______________________________________________ postmodern-devel mailing list postmodern-devel(a)common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel

1 0

[postmodern-devel] Get keys out of dao-class
by Phil Marneweck 27 Feb '09

27 Feb '09

Hi How would one find out what the keys are on a dao-class? I have scratched around in the code and found dao-column-fields, but the equavilant for keys seems to be dao-keys but I cant find a defun for it...I am not even sure it should have a defun. Regards Phil

2 1

[postmodern-devel] *silently-truncate-ratios*
by Attila Lendvai 06 Feb '09

06 Feb '09

> Thanks for the patch. I've revised the writer function a bit -- there > was some useless cruft in it, and you misspelled floating as foating > -- and added a switch to turn off the raising of errors, thanks for the cleanup, it was just a quick'n'dirty result of a longer debugging session... > *silently-truncate-literals*, which defaults to T, since I suspect not > everyone is happy with errors like that popping up. You can set it to > NIL and get the behaviour you're after. ...but i really don't like the default of that special. rationale: 1) you start using the lib, do some calculations involving db storage, some time later realize that they are somewhat off, start digging where the hell it goes wrong, waste a lot of time looking at too many things until you finally realize that 7/10 written to the database silently comes back as something else than 7/10. imho, that special should default to NIL for the least surprises and for bringing the symptoms of the error *much* closer to their cause. then: 2) user stars using lib, stores ratios in db, at some point faces a descriptive error message which includes a hint about the above mentioned special, reads up on the issue if necessary, based on necessary understanding of the issue decides to add required coercions to his code or to set/bind the special to T. summing up all the time people would spend with the use-case 1) is a lot more than people would spend with 2). now, i don't care much, because i've been through 1) already... :) but i suggest these changes for everyone's good. i've pushed what i think to my repo, but i will not stick to it. if you decide to keep things as they are, i'll eventually unpull my patch to enjoy the benefit of the zero distance from the official repo. hth, -- attila ps: i've cc'd the list if other lib users want to speak up on the issue...

2 2

[postmodern-devel] timestamps return format
by Timur Sufiev 02 Feb '09

02 Feb '09

Hi! In order to convert timestamps from unix time to GMT strings I used the following select query: SELECT TIMESTAMP 'epoch' + 1195374767 * INTERVAL '1 second' or, the s-sql analogue `(:select (:+ (:type "epoch" timestamp) (:* ,unix-time (:type "1 second" interval)))) Surprisignly, it returned timestamps as numbers, not strings. After some investigation the reason of that behaviour became clear. Consider 2 following queries. (pomo:query (:select 'timestamp :from 'sales :where (:and (:= 'vend-machine-id 2) (:< 'timestamp "2009-01-12")))) (("2009-01-11 18:37:18+03") ("2009-01-11 23:59:59+03") ("2009-01-11 23:59:59+03") ("2009-01-11 23:59:59+03") ("2009-01-11 23:59:59+03") ("2009-01-11 23:59:59+03")) (pomo:query (:select (:type 'timestamp timestamp) :from 'sales :where (:and (:= 'vend-machine-id 2) (:< 'timestamp "2009-01-12")))) ((3440687838) (3440707199) (3440707199) (3440707199) (3440707199) (3440707199)) So, type-cast to TIMESTAMP makes postmodern to return timestamps as numbers. How is it possible to return unix-time as GMT strings via postmodern sql queries? -- Timur Sufiev

2 2

[postmodern-devel] :cascade op patch
by Timur Sufiev 19 Jan '09

19 Jan '09

Sometimes it is convenient to drop objects recursively (by DROP <object-type> <object-name> CASCADE). The following patch allows this in a s-sql fashion. -- Timur Sufiev

2 1

[postmodern-devel] Looking for hints on converting from clsql to postmodern
by Sabra Crolleton 29 Dec '08

29 Dec '08

One of our postgresql databases has a heavy proportion of foreign language text (all encoded in utf-8). I was starting to learn lisp by porting a webapplication and got part way into it before I realized that using clsql may require me to manually encode and decode everything from latin to utf-8. It was suggested that postmodern may be a way out of that. The app is still in early stages, so I'm hoping that converting from clsql to postmodern won't be too bad, but any hints on things to watch out would be appreciated. Sabra

2 1

[postmodern-devel] Patch: query callback support
by Maciej Pasternacki 22 Dec '08

22 Dec '08

Hello, Recently I wanted to start profiling my webapp and display some stats in footer, namely number of queries and total time spent waiting for the database. Only option provided by Postmodern was using CL- POSTGRES:*QUERY-LOG* and reparsing its output, but this would be just awful Perl-like approach, and the time given would be very inaccurate (most of my queries are short, and query log rounds time to full milliseconds, so most queries show as 0ms). I added *QUERY-CALLBACK* support for cl-postgres, which makes CL-Postgres call given function with query string and internal time units spent after every query, moved *QUERY-LOG* support to separate function LOG-QUERY, which I made default value of *QUERY-CALLBACK* for backwards compatibility. Darcs changeset is attached. Regards, Maciej. -- Maciej Pasternacki -><- http://www.pasternacki.net/ -><- http://www.3ofcoins.net/

2 2

[postmodern-devel] s-sql patch for postmodern 1.13: separate condition
by Timur Sufiev 17 Dec '08

17 Dec '08

We learned that it is useful to a) have separate condition to distinguish s-sql parsing errors from others b) have :delete-from syntax extended: sometimes it is necessary to return keys of deleted rows. Both patches (generated by git) are in attach. It would be very nice to see them in upstream.

2 2

[postmodern-devel] Building s-sql on the fly
by Phil 11 Dec '08

11 Dec '08

Hi I am looking for an example of how to create a s-sql query on the fly. I am sure I saw something like that along the line on some website but I cant find it again. Thanx

4 7

[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

[postmodern-devel] Storing Lists
by Mark Slamin 29 Sep '08

29 Sep '08

How do I insert a list into a single field of a single record in the database? Trying to insert (A B C) yields type errors if database type is set to text or varchar. Is there another data type I should use? Does the list need to be modified somehow? I need to be able to store and retrieve a list as easily as possible. Thanks. Mark Slamin

4 4

[postmodern-devel] Create-table dynamic table name
by Mark Slamin 21 Sep '08

21 Sep '08

Hi. How do I use a variable as a table name with create-table? The following always takes 'tableName' as the name rather than the value of tableName: (sql (:create-table tableName ((name :type string) (address :type string)))) :raw doesn't seem to work. Thanks Mark

2 1

[postmodern-devel] character encoding
by Roman Budzianowski 11 Sep '08

11 Sep '08

I am trying to retrieve records from a db with SQL_ASCII. Any advice on how to deal with it? I don't see a way to change the encoding for a connection. Invalid byte at start of character: 0x99 [Condition of type TRIVIAL-UTF-8:UTF-8-DECODING-ERROR] I don't think I can change the encoding of the db. Roman

2 8

[postmodern-devel] Release 1.13
by Marijn Haverbeke 28 Aug '08

28 Aug '08

There were a handful of small fixes still sitting around, as well as the deftable addition. It has been four months since 1.12, so: 1.13! Champagne all around. Best, Marijn

1 0

[postmodern-devel] darcs patch: Correct rational (double-float) formatting
by Arjan Wekking 28 Jul '08

28 Jul '08

Fri Jul 25 15:52:12 CEST 2008 Arjan Wekking <arjan(a)streamtech.nl> * Correct rational (double-float) formatting On Clozure CL (PPC32), (format "~f" (coerce 1/123 'double-float)) returns "0.008130081300813009D0" which is not a number syntax PostgreSQL understands. In order to be sure that a format is used that is always supported, the formatting string was changed to generate the number in exponential notation which is accepted by PostgreSQL and which can be reliably generated by at least SBCL and Clozure CL (only CLs I've tested). The modified control string in this patch ("~,,,,,,'EE") will generate for the rational 1/123 "8.130081300813009E-3" which is accepted and interpreted properly by PostgreSQL.

2 3