postmodern-devel February 2009

postmodern-devel@common-lisp.net

4 participants
5 discussions

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

28 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

postmodern-devel February 2009