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

[postmodern-devel] postmodern, pg, cl-rdbms
by Attila Lendvai 27 Aug '07

27 Aug '07

hello list, i've recently found postmodern on cl.net, and i was wondering that there seems to be a massive amount of duplication of efforts among the following projects: - pg is a long-time postgresql socket based lib: http://common-lisp.net/project/pg/ - cl-rdbms (our fresh clsql replacement, http://common-lisp.net/project/cl-rdbms/ ) which aims to be a backend independent sql lib, just like clsql, with sexp sql syntax ( see http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cl-rdbms-cl-rdbms;a=… for a quick impression ). it has a single backend for now, based on pg. - and postmodern which is something like a mixture of pg and cl-rdbms we should bring out the best of these... my first impression of postmodern is that it's more modern and better organized code then pg which is good. and to also write actual suggestions besides to this rant, i'd use http://common-lisp.net/project/local-time/ as the date/time abstraction data type. it supports timezones and has a string parser/printer. and fyi, trivial-sockets seems to be a dead project. i've tried to contact the author several times with patches and there wasn't any response; #lisp is on the same opinion. usocket at least welcomes patches, but it's not really important if t-s can already do everything needed. any toughts? -- - attila "- The truth is that I've been too considerate, and so became unintentionally cruel... - I understand. - No, you don't understand! We don't speak the same language!" (Ingmar Bergman - Smultronstället)

3 10

[postmodern-devel] 0.22 regression?
by Feng Hou 28 Jan '07

28 Jan '07

CL-USER> (deftable test-data () ((field1 :type integer) (field2 :type (or string db-null)) (field3 :type (numeric 10 3))) (:indices field1 field3)) CL-USER> (create-table 'test-data) Database error 42601: syntax error at end of input Query: CREATE TABLE test_data (field1 INTEGER NOT NULL, field2 TEXT [Condition of type DATABASE-ERROR] 3: (CL-POSTGRES:EXEC-QUERY #<DATABASE-CONNECTION {BF30B39}> "CREATE TABLE test_data (field1 INTEGER NOT NULL, field2 TEXT" CL-POSTGRES:IGNORE-ROW-READER) Locals: CL-POSTGRES::CONNECTION = #<DATABASE-CONNECTION {BF30B39}> CL-POSTGRES::QUERY = "CREATE TABLE test_data (field1 INTEGER NOT NULL, field2 TEXT" CL-POSTGRES:ROW-READER = CL-POSTGRES:IGNORE-ROW-READER

1 0

[postmodern-devel] Re: postmodern-devel Digest, Vol 2, Issue 4
by Giorgos Pontikakis 27 Jan '07

27 Jan '07

Hello Marijn, Sorry for the belated response, I had been busy through the week and I checked my email just today | I released verion .21, which should solve your first two problems. Great, I will try the new version. Thanks | Haven't quite decided on the syntax for foreign keys, maybe | :create-table can look like defclass too: | | (:create-table 'my-table | ((slot-a :type integer :foreign-key (my-other-table id) :default | 55) (slot-b :type (or null (string 24))) | (:primary-key slot-a) | (:foreign-key (slot-a slot-b) (yet-another-table a b) | (:unique-index slot-b)) ;; Not really part of CREATE TABLE, but | hey, why not? | Then deftable doesn't have to do as much transforming on the | definition and can remain simple. | | Also, I'm not sure how to handle the creation of a set of tables | that contain foreign keys -- since they have to be created in the | right order. Altering them is even more tricky. Maybe I'll default | to deferrable foreign keys, and turn on deferring when messing with | the table scheme. | | Let me know what you think. | Well, I don't know, sorry. I am an amateur and my real job does not involve computers. I have no experience in sql. I just noticed that you released 0.22. I'll try to use it and I'll report if I have anything constructive to say. Thanks again -- Giorgos

1 0

[postmodern-devel] Release 0.22
by Marijn Haverbeke 27 Jan '07

27 Jan '07

Hello list, Version .22 of Postmodern has been released, which adds constraints (uniqueness, checks, foreign keys) and default values to :create-table's syntax (not backwards compatible), and changes the approach to transactions somewhat (also a small syntax change). Marijn

1 0

[postmodern-devel] ~ infix operator
by Giorgos Pontikakis 24 Jan '07

24 Jan '07

Hi, First, I think this is an very good library and I have to thank you for releasing it. The documentation is exceptionally good, congratulations for your effort. Second, I noticed that the ~ infix operator from PostgreSQL for regular expressions is not included in the def-infix-ops (file s-sql.lisp). I suppose that this is because it conflicts with the bitwise NOT operator with the same name, which is defined after a few lines. For the time being, I just changed the bitwise NOT to :~~ and added the :~ to the def-infix-ops forms. Is this something you overlooked or is there another way to access regular expressions functionality? Third, since I see you care about the documentation, I think you should point out in the documentation that the deftable form must define the table columns in the same order with its PostgreSQL counterpart, since you use the * abbreviation in the get-dao select statement. Otherwise, the get-dao does not work. Finally, is there a way to access the constraints of an SQL table from the Lisp side? I have not managed to find anything related yet. That's all for the time being. Once more, thank you very much for the library. Best regards, Giorgos Pontikakis

2 2