postmodern-devel

postmodern-devel@common-lisp.net

252 discussions

[postmodern-devel] Binary and unary operators
by Ivan Boldyrev 09 Jan '08

09 Jan '08

1. You are missing such operators like || and && (former is string concatenation, latter is tests overlapping geometric objects). There are also a. math: !, !!, #, >>, <<. b. geometric: ##, @@, @-@, ~=, <->, &<, &>, <<|, |>>, &<|, |&>, <^, >^, ?#, ?|, ?-|, ?||, @>, <@. c. network: <<=, >>=. ?| is both binary and unary operator, ! is postfix (but is equivalent to prefix !!, so you may define :! that expands to prefix !! or just :!! that expands to !!). There are also another operators like @, but they have functions-substitutions (@ x <=> abs(x)). psql's command \do (describe operators) also lists other operators. 2. As PSQL allows defining own operators, I think it worth exporting s-sql::def-infix-ops or creating some more flexible user macro (one might prefer to use :concat instead of :\|\|). With such facility you don't need to define such rare-used operators like @-@ and ?-|, allowing user to define them. -- Ivan Boldyrev Violets are red Roses are blue It's amazing what DNA splicing can do.

2 6

[postmodern-devel] Performance patch
by Ivan Boldyrev 07 Jan '08

07 Jan '08

My application uses quite long and complex query, and profiling showed that slowest function is SQL-COMPILE. First I reimplemented it with S-SQL::STRCAT, but then I thought: what if it will hit CALL-ARGUMENTS-LIMIT (it is only 4096 on GNU Clisp!)? So I changed implementation of S-SQL:STRCAT to get list as the only argument, not as &rest. SQL-COMPILE is much faster and consumes on my query 10 times less memory. As SQL-COMPILE is usually called on run time, not compilation time, I think it is very important. --- old/s-sql/s-sql.lisp~ 2008-01-07 20:05:17.000000000 +0600 +++ new/s-sql/s-sql.lisp 2008-01-07 23:26:03.000000000 +0600 @@ -25,7 +25,7 @@ ;; Utils -(defun strcat (&rest args) +(defun strcat (args) "Concatenate a list of strings into a single one." (let ((result (make-string (reduce #'+ args :initial-value 0 :key 'length)))) (loop :for pos = 0 :then (+ pos (length arg)) @@ -36,11 +36,11 @@ (defun implode (sep list) "Reduce a list of strings to a single string, inserting a separator between them." - (apply 'strcat - (loop :for element :on list - :collect (car element) - :if (cdr element) - :collect sep))) + (strcat + (loop :for element :on list + :collect (car element) + :if (cdr element) + :collect sep))) (defun split-on-keywords% (shape list) "Helper function for split-on-keywords. Extracts the values @@ -338,11 +338,11 @@ (let ((list (reduce-strings (sql-expand form)))) (if (= 1 (length list)) (car list) - `(strcat ,@list)))) + `(strcat (list ,@list))))) (defun sql-compile (form) (let ((*expand-runtime* t)) - (car (reduce-strings (sql-expand form))))) + (strcat (sql-expand form)))) ;; The reader syntax. @@ -378,7 +378,7 @@ (declare (type (member t :both nil) class)) (cond ((cdr args) - `("(" ,@(sql-expand-list args (strcat " " operator " ")) ")")) + `("(" ,@(sql-expand-list args (strcat (list " " operator " "))) ")")) ((eq class t) (sql-expand (first args))) ((eq class :both) -- Ivan Boldyrev Life! Don't talk to me about life.

2 1

[postmodern-devel] WITH-SAVEPOINT macro
by Ivan Boldyrev 06 Jan '08

06 Jan '08

WITH-SAVEPOINT macro is modelled after WITH-TRANSACTION. I would be glad to see it in 1.05 :) -- Ivan Boldyrev Assembly of a Japanese bicycle requires greatest peace of spirit.

2 5

[postmodern-devel] Bug report: Incorrect handling of SIMPLE-DATE types in S-SQL
by Ivan Boldyrev 05 Jan '08

05 Jan '08

This doesn't work: ,---- | (postmodern:query | (:select (:- :localtimestamp | (simple-date:encode-interval :hour 2 :minute 10)))) | | Database error 22007: invalid input syntax for type timestamp: "2 hours 10 minutes " | Query: (SELECT (localtimestamp - '2 hours 10 minutes ')) `---- This does work: ,---- | (postmodern:query | (:select (:- :localtimestamp (:raw "interval '2 hours 10 minutes'")))) `---- It was tested with PostgreSQL 8.0.13 and 8.2.4. SQL-IZE methods for SIMPLE-DATE objects should return escaped strings like "interval '2 hours 10 minutes'", not just "2 hours 10 minutes", and second value of SQL-IZE must be NIL: b ,---- | (:method ((arg simple-date:date)) | (multiple-value-bind (year month day) (simple-date:decode-date arg) | (format nil "date ~A" | (sql-escape-string (format nil "~4,'0d-~2,'0d-~2,'0d" year month day))))) `---- (Untested!) Perhaps, sql-escape-string can be omitted: the output has no dangerous characters anyway. ,---- | (:method ((arg simple-date:date)) | (multiple-value-bind (year month day) (simple-date:decode-date arg) | (format nil "date '~4,'0d-~2,'0d-~2,'0d'" year month day))) `---- -- Ivan Boldyrev Violets are red, Roses are blue. // I'm schizophrenic, And so am I.

2 2

[postmodern-devel] Inserting into related tables
by Ivan Boldyrev 05 Jan '08

05 Jan '08

I don't quite understand how to do inserts into related table. For example, we have table 'items' with field 'producer_id' and table 'producer' with 'producer_id' and 'producer_name' fields: ,---- | (deftable item () | ((producer-id :type (or integer db-null)") | ... ; Other fields | ) | (:auto-id id)) | | (postmodern:deftable producers () | ((producer-name :type (string 50))) | (:auto-id producer-id) | (:indices producer)) | | ;; Add unique index manually | (postmodern:execute | (:create-unique-index 'producers-name-uniq-idx | :on 'producers | :fields 'producer-name)) `---- When we add new item to the database, producer may exist or may be new. We have to check producer's existense and add it to table if required. The only safe way to do it seems to be ,---- | ;; We ignore error if name exists. But what about other errors? | (ignore-errors | (let ((id (postmodern:next-id 'producers))) | (postmodern:execute | (:insert-into table :set | 'producer-id id | 'producer-name name)))) | | ;; Now get ID to insert into items.producer-id. | (postmodern:query | (:select 'producer-id :from table :where (:= 'producer-name name)) | :single) `---- However, on each insertion we increment producers-producer-id-seq even if producer name already exists in the table. This is somewhat clumsy. And faulty query wrapped with ignore-errors doesn't work with transactions. Is there any other postmodern-way? -- Ivan Boldyrev XML -- new language of ML family.

2 9

[postmodern-devel] Tiny patch for Allegro Common Lisp
by Ivan Boldyrev 28 Dec '07

28 Dec '07

I have tested Postmodern with Allegro Common Lisp 8.1 Experess and found that it trivial-utf8 is not loaded and non-latin charsets do not work. The reason is that ACL doesn't put :unicode in *features*, but puts :ics (International Character Set?). The patch attached fixes that. -- Ivan Boldyrev

2 1

[postmodern-devel] development plans for discussion
by Attila Lendvai 19 Nov '07

19 Nov '07

hi! i have two changes planned: 1) use babel for string encoding/decoding ( http://common-lisp.net/~loliveira/soc07/babel/ ). the rationale is that it's a very nice cross platform unicode lib which is also very fast. Marijn, i hope you will not take it as offense! i know trivial-utf8 is your work, but i hope the speed and the de facto standardness of babel compensates. (Luis will give babel more publicity in the next weeks, but it's available for months now and i'm using it without problems). 2) use iolib for the socket code. i would like to do that because we are experiencing problems when dealing with sockets on sbcl when the system is under heavy load. another reason is that iolib is another nice piece of code, although its also more heavyweight then usocket and also posix-only (currently). i know you prefer simple libs, just like with ironclad/md5, but we need stability and this seems to be the simplest way to achive it. what do you think of these changes? -- attila

2 3

[postmodern-devel] Warnings from bordeaux-threads
by Jens Teich 17 Nov '07

17 Nov '07

I have a problem with warnings from bordeaux-threads. These warnings are no problem when I load manually on Lispworks and SBCL. But when I try to deliver a stand-alone application on Lispworks the delivery process stops at these warnings. I reported the problem to bordeaux-threads mailinglist. They are as follows: | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\bordeaux-threads.ofasl | ; Loading fasl file d:\Projekte\Lisp\bordeaux-threads\src\lispworks.ofasl | Warning: (METHOD | MAKE-THREAD | (T)) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). | Warning: (METHOD | MAKE-LOCK | NIL) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). | Warning: (DEFMACRO WITH-LOCK-HELD) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). | Warning: (METHOD | THREAD-YIELD | NIL) being redefined in d:\Projekte\Lisp\bordeaux- | threads\src\lispworks.lisp (previously in d:\Projekte\Lisp\bordeaux- | threads\src\bordeaux-threads.lisp). Is there a way for postmodern to load without bordeux-threads? I think on Lispworks I don't need this. I tried the following (changed t and nil) | ;; Change this to manually turn threading support on or off. | (defparameter *threads* #+(or allegro armedbear cmu corman (and digitool ccl-5.1) | ecl lispworks openmcl sbcl) nil | #-(or allegro armedbear cmu corman (and digitool ccl-5.1) | ecl lispworks openmcl sbcl) t) but there is some resistance: | Loading fasl file d:\Projekte\Lisp\postmodern-1.02\postmodern\connect.ofasl | | Error: Package BORDEAUX-THREADS not found. | 1 Get another package name. | ... Jens

2 2

[postmodern-devel] views
by Joe Corneli 15 Nov '07

15 Nov '07

So, Postmodern doesn't seem to have very minimal support for views (just `list-views' and `view-exists-p'), but I assume I can still work with them? Any tips on that?

3 2

[postmodern-devel] connecting
by Joe Corneli 14 Nov '07

14 Nov '07

I can run psql from the shell -- % psql Welcome to psql 7.4.17, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit joe=# but trying to connect to PostgreSQL with Postmodern currently fails: CL-USER> (connect-toplevel "joe" "joe" "" "localhost") Backtrace: 0: (USOCKET::HANDLE-CONDITION #<SB-BSD-SOCKETS:CONNECTION-REFUSED-ERROR {A7CD821}> #<USOCKET:STREAM-USOCKET {A7B8831}>) 1: (USOCKET:SOCKET-CONNECT "localhost" 5432) 2: (CL-POSTGRES::INITIATE-CONNECTION #<DATABASE-CONNECTION {A7B84C9}>) 3: (CL-POSTGRES:OPEN-DATABASE "joe" "joe" "" "localhost" 5432) 4: (CONNECT-TOPLEVEL "joe" "joe" "" "localhost") 5: (SB-INT:SIMPLE-EVAL-IN-LEXENV (CONNECT-TOPLEVEL "joe" "joe" "" "localhost") #<NULL-LEXENV>) Can you give me any ideas on how to get this connection working? This is a fresh install of Postmodern, but I am using some old ASDF files for dependences, do you think that could be the problem?

2 2

← Newer
1
...
18
19
20
21
22
23
24
25
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