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

[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

[postmodern-devel] Table extra options in DAO definition
by Rafał Strzaliński 14 Jul '08

14 Jul '08

Hi, I'm attaching a patch that allows to add table extra options ( :check :unique ..) to a DAO definition. Sample: (defclass account () ((id :col-type serial ) (login :col-type (varchar 255) :accessor login :initarg :login) (password :col-type (varchar 255) :accessor password :initarg :password) (created_at :col-type timestamp :accessor created-at :initform (now-timestamp))) (:unique name) (:metaclass dao-class) (:keys id) (:extra-options (:unique login)) (:table-name account.account)) -- Best regards, Rafal Strzalinski (nabla) http://nablaone.net

2 4

[postmodern-devel] FULL OUTER JOIN clause in s-sql (:outer-join)
by Timur Sufiev 04 Jul '08

04 Jul '08

I've noticed recently that :outer-join spec isn't supported by s-sql, although it is mentioned in reference for postmodern-1.12. So i've added it myself.

2 2

[postmodern-devel] prepare macro syntax
by Roman Budzianowski 19 Jun '08

19 Jun '08

Hi Marijn, (prepare q) where q is bound to a query works fine, however (prepare (get 'foo 'query)) doesn't complain, but generates incorrect closure. Easy workaround, but is this a bug? Thanks, Roman

2 3

[postmodern-devel] the reason why i'd like an iolib network backend instead of usocket
by Attila Lendvai 19 Jun '08

19 Jun '08

dear list, after some uptime, all of a sudden i was getting these errors on our server. this is probably something going awry inside sb-bsd-sockets. as time permits, i'll experiment with an iolib based network backend for cl-postgres. - attila *** At: 2008-06-14T03:47:32.266936+02:00 *** In thread: http worker 34 / serving request / CALL-WITH-SERVER-ERROR-HANDLER / HANDLE-TOPLEVEL-CONDITION *** Error: Socket error in \"socket\": EPROTONOSUPPORT (Protocol not supported) *** Backtrace is: 000: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> #<ESEHO-PRESENTATION::ESEHO-APPLICATION \" /\" {911C645}> #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 001: ((HU.DWIM.WUI:HANDLE-TOPLEVEL-CONDITION :AROUND (T T)) #<ESEHO-PRESENTATION::ESEHO-APPLICATION \"/\" {911C645}> #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 002: ((FLET HU.DWIM.WUI::HANDLE-REQUEST-ERROR) #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 003: ((LAMBDA (ERROR)) #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) 004: (SIGNAL #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>) [:EXTERNAL] 005: (ERROR SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR) [:EXTERNAL] 006: (SB-BSD-SOCKETS:SOCKET-ERROR \"socket\") 007: (SB-BSD-SOCKETS:SOCKET-ERROR \"socket\") [:EXTERNAL] 008: ((SHARED-INITIALIZE :AFTER (SB-BSD-SOCKETS:SOCKET T)) #<error printing object: NIL>) [:EXTERNAL] 009: ((LAMBDA ())) 010: (USOCKET:SOCKET-CONNECT \"database\" 5432) [:EXTERNAL] 011: (CL-POSTGRES::INITIATE-CONNECTION #<CL-POSTGRES:DATABASE-CONNECTION {107C3F11}>) 012: (CL-POSTGRES:OPEN-DATABASE \"eseho\" \"eseho\" \"szupertitok\" \"database\" 5432 :NO) 013: ((CL-RDBMS.POSTGRESQL::CONNECTION-OF :AROUND (CL-RDBMS.POSTGRESQL::POSTGRESQL-POSTMODERN-TRANSACTION)) #<DWIM-META-MODEL::TRANSACTION :begin-executed-p #t {107AB379}>) 0

2 1

[postmodern-devel] db-null problem
by Roman Budzianowski 13 Jun '08

13 Jun '08

There seems to be a problem with exporting of 'db-null type: CL-USER> (pomo:sql (:create-table foo ((age :type (or db-null integer) :default :null)))) "CREATE TABLE foo (age OR NOT NULL DEFAULT NULL)" =========> error! CL-USER> (in-package :pomo) #<The POSTMODERN package> POMO> (pomo:sql (:create-table foo ((age :type (or db-null integer) :default :null)))) "CREATE TABLE foo (age INTEGER DEFAULT NULL)" POMO> Roman

2 1