postmodern-devel

postmodern-devel@common-lisp.net

252 discussions

[postmodern-devel] sql injection
by Phil Marneweck 25 Jun '10

25 Jun '10

Hi How susceptible is dao objects to sql injection and what measures would be suggested to prevent sql injection if it is possible with dao objects. Thank You

2 2

[postmodern-devel] Local connection to Postgresql under FreeBSD
by rrl 18 May '10

18 May '10

Hi, I can connect to Postgresql using a Unix socket with sbcl by passing :unix as a host. The problem is that under FreeBSD, the default directory for the socket is ``/tmp'' and not ``/var/run/postgresql''. Here's a quick fix that solves the problem: --- public.lisp.orig 2010-04-14 21:41:39.000000000 +0300 +++ public.lisp 2010-05-15 11:21:56.000000000 +0300 @@ -47,7 +47,9 @@ #+(and sbcl unix) (defun sb-unix-socket-connect (port) (let ((sock (make-instance 'sb-bsd-sockets:local-socket :type :stream)) - (addr (format nil "/var/run/postgresql/.s.PGSQL.~a" port))) + (addr (format nil "~a/.s.PGSQL.~a" + #-freebsd "/var/run/postgresql" #+freebsd "/tmp" + port))) (sb-bsd-sockets:socket-connect sock addr) (sb-bsd-sockets:socket-make-stream sock :input t :output t :element-type '(unsigned-byte 8)))) Maybe a better fix would be to define a variable for the socket directory and let the user set it himself.

2 1

[postmodern-devel] Compile error: about to bind S-SQL::CH to NIL, which is not of type CHARACTER.
by Frank Goenninger 16 May '10

16 May '10

Hi there, being totally new to postmodern I have encountered the following problem: (Environment: AllegroCL Express Edition on Mac OS X, newest postmodern bits from github) ;;; Compiling file ;;; /opt/common-lisp/packages/postmodern/postmodern/util.lisp ; While compiling LIST-TABLES: about to bind S-SQL::CH to NIL, which is not of type CHARACTER. [Condition of type TYPE-ERROR] ... not digging into it yet, I wonder if anybody has seen this, too ... Thanks!! Regards Frank

2 3

[postmodern-devel] Passing a list to a prepared query
by Sebastian Tennant 16 May '10

16 May '10

Hi, I'd like to do this: (defprepared addresses-by-ids "SELECT address FROM users WHERE id IN $1" :column) and then call it like so: CLUSER> (addresses-by-ids "(1,2,3)") Is this possible? I've tried a few different approaches but keep getting errors. Many thanks for great software by the way. Seb -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap

2 2

[postmodern-devel] cl-postgres/sbcl crashes with bogus stack frame
by Andrew Golding 07 May '10

07 May '10

Kind of a general heads-up. I have actually been using CLSQL and saw the bit in one of the older messages about getting a similar result in CLSQL. Anyways, if the foreign code messes with signal handling, even signals SBCL isn't currently using, it has the potential to crash the program. I'll try to have a look at postmodern this weekend and see if I can reproduce and solve the problem.

1 0

[postmodern-devel] cl-postgres/sbcl crashes with bogus stack frame
by david thompson 06 May '10

06 May '10

Any ideas what might trigger cl-postgres (postmodern 1.14) coming to its knees with the backtrace shown below? No error or condition description is given - sbcl (1.0.28) just retires from active duty and drops into the debugger with the ("bogus stack frame") indication. The postgresql server (8.3) log doesn't have any indication of trouble at the time cl-postgres seems to run into trouble. This seems to only happen intermittently (every few thousand queries), irreproducibly (doesn't seem to be associated with a specific query or anything along those lines), and only when the postgresql server is being utilized by several lisp instances concurrently. Thanks in advance for any input/ideas/troubleshooting suggestions... - Alan ... 32: ("bogus stack frame") 33: (SB-IMPL::SUB-SUB-SERVE-EVENT NIL NIL) 34: (SB-IMPL::SUB-SERVE-EVENT NIL NIL NIL) 35: (SB-SYS:WAIT-UNTIL-FD-USABLE 5 :INPUT NIL) 36: (SB-IMPL::REFILL-INPUT-BUFFER #<SB-SYS:FD-STREAM for "a socket" {C265BA9}>) 37: (SB-IMPL::INPUT-UNSIGNED-8BIT-BYTE #<SB-SYS:FD-STREAM for "a socket" {C265BA9}> T NIL) 38: (CL-POSTGRES::SKIP-BYTES #<unavailable argument> #<unavailable argument>) 39: (CL-POSTGRES::TRY-TO-SYNC #<SB-SYS:FD-STREAM for "a socket" {C265BA9}> T) 40: ((FLET #:CLEANUP-FUN-[FORM-FUN-[SEND-QUERY]389]390))[:CLEANUP] 41: (CL-POSTGRES::SEND-QUERY #<unavailable argument> #<unavailable argument> #<unavailable argument>) 42: ((LABELS #:G161)) 43: (SQLG::QUERY-CORE "select program from programs where programskey = '192828' ;" 20 #<unused argument>)

4 5

[postmodern-devel] NIL interpreted as Boolean
by Patrick May 06 May '10

06 May '10

I have a class that looks something like this: (defclass call-request () ((phone-number :initarg :phone-number :accessor phone-number :type string :col-type string) (call-time :initarg :callback-time :accessor callback-time :type (or null simple-date:timestamp :col-type (or db-null numeric) :initform nil) (extension :initarg :extension :accessor extension :type (or string null) :col-type (or db-null string) :initform nil)) (:metaclass postmodern:dao-class) (:table-name "call_request") (:keys phone-number) (:documentation "A request to be called.")) When I try to insert a call-request with no call-time or extension, I get the error: Database error 42804: column "call_time" is of type time with time zone but expression is of type boolean You will need to rewrite or cast the expression. Query: INSERT INTO call_request (extension, callback_time, phone_number) VALUES (false, false, E'8005551212') [Condition of type CL-POSTGRES-ERROR:SYNTAX-ERROR-OR-ACCESS-VIOLATION] How do I make Postmodern interpret nil as db-null rather than boolean? Thanks, Patrick

3 6

[postmodern-devel] Examples of using CLOS interface
by Patrick May 15 Apr '10

15 Apr '10

I've recently found Postmodern and it looks like a nice, lighter weight alternative to CL-SQL. Is there any detailed documentation for using Postmodern with CLOS? How about a richer example than that in the Database access objects section of the manual? Thanks, Patrick

1 0

[postmodern-devel] PATCH: New query formats - plists and plist
by Andrey Moskvitin 14 Apr '10

14 Apr '10

Hi, I propose to add new query formats: diff --git a/doc/postmodern.html b/doc/postmodern.html index 3691ae8..9ac466f 100644 --- a/doc/postmodern.html +++ b/doc/postmodern.html @@ -202,6 +202,10 @@ row.</td></tr> <tr><td><code>:list</code>, <code>:row</code></td><td>Return a single row as a list.</td></tr> + <tr><td><code>:plists</code></td><td>Return a list of plists which map column + names to values,with the names represented as + keywords.</td></tr> + <tr><td><code>:plist</code></td><td>Return a single row as an plist.</td></tr> <tr><td><code>:alists</code></td><td>Return a list of alists which map column names to values,with the names represented as keywords.</td></tr> diff --git a/postmodern/query.lisp b/postmodern/query.lisp index 3e5bfa5..921d03d 100644 --- a/postmodern/query.lisp +++ b/postmodern/query.lisp @@ -9,6 +9,15 @@ :for symbol :in symbols :collect (cons symbol (next-field field)))))) +;; Like symbol-alist-row-reader, but return plist +(def-row-reader symbol-plist-row-reader (fields) + (let ((symbols (map 'list (lambda (desc) (from-sql-name (field-name desc))) fields))) + (loop :while (next-row) + :collect (loop :for field :across fields + :for symbol :in symbols + :collect symbol + :collect (next-field field))))) + ;; A row-reader for reading only a single column, and returning a list ;; of single values. (def-row-reader column-row-reader (fields) @@ -22,6 +31,8 @@ (:list list-row-reader t) (:rows list-row-reader nil) (:row list-row-reader t) + (:plists symbol-plist-row-reader nil) + (:plist symbol-plist-row-reader t) (:alists symbol-alist-row-reader nil) (:alist symbol-alist-row-reader t) (:str-alists alist-row-reader nil) Moskvitin Andrey

3 6

[postmodern-devel] PATCH: Add support for asynchronous notifications
by Zach Beane 08 Apr '10

08 Apr '10

Attached is a patch that adds Postmodern support for asynchronous notifications, as documented here: http://www.postgresql.org/docs/current/static/sql-listen.html http://www.postgresql.org/docs/current/static/sql-notify.html http://www.postgresql.org/docs/current/static/sql-unlisten.html and http://www.postgresql.org/docs/current/interactive/protocol-message-formats… (under "NotificationResponse") It updates MESSAGE-CASE to watch for async notifications and, by default, issue a warning that looks very similar to what the psql client displays for async notifications: WARNING: Asynchornous notification "lisp" received from server process with PID 22063. It also adds a blocking function, WAIT-FOR-NOTIFICATION, that adds a handler-bind around the warning and returns the notification data when a notification is received. The patch isn't complete, though -- I wasn't sure how best to integrate the new public function, condition, and condition accessors into the documentation. How should I proceed? Zach

2 1

← Newer
1
...
8
9
10
11
12
13
14
...
26
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

postmodern-devel