00:17:15 ddp [~ddp@cpe-75-85-147-17.hawaii.res.rr.com] has joined #ccl
00:26:59 -!- rme [~rme@50.43.184.114] has quit [Quit: rme]
00:30:07 kmcorbett [~kmcorbett@173-9-35-41-NewEngland.hfc.comcastbusiness.net] has joined #ccl
00:40:32 rme [~rme@50.43.184.114] has joined #ccl
00:50:46 -!- kmcorbett [~kmcorbett@173-9-35-41-NewEngland.hfc.comcastbusiness.net] has quit [Quit: Quit]
01:04:31 -!- ddp [~ddp@cpe-75-85-147-17.hawaii.res.rr.com] has quit [Quit: ddp]
01:06:30 ddp [~ddp@cpe-75-85-147-17.hawaii.res.rr.com] has joined #ccl
02:16:38 gko [~gko@220.228.255.202] has joined #ccl
02:38:01 -!- rme [rme@833E80F1.333FC83A.699BA7A6.IP] has quit [Quit: rme]
02:38:01 -!- rme [~rme@50.43.184.114] has quit [Quit: rme]
02:40:07 -!- alms_ [~alms_@209-6-130-32.c3-0.bkl-ubr1.sbo-bkl.ma.cable.rcn.com] has quit [Quit: alms_]
03:54:24 -!- ddp [~ddp@cpe-75-85-147-17.hawaii.res.rr.com] has quit [Quit: ddp]
04:43:47 -!- gko [~gko@220.228.255.202] has quit [Ping timeout: 260 seconds]
06:28:53 dnm [~dnm@li97-254.members.linode.com] has joined #ccl
07:17:08 -!- milanj [~milanj_@178-223-128-113.dynamic.isp.telekom.rs] has quit [Ping timeout: 240 seconds]
08:35:29 jdz [~jdz@193.206.22.97] has joined #ccl
09:46:21 milanj [~milanj_@178-223-128-113.dynamic.isp.telekom.rs] has joined #ccl
10:13:19 -!- peccu1 is now known as PECCU
12:01:07 pbgc [~pbgc@bl20-175-98.dsl.telepac.pt] has joined #ccl
13:18:19 alms_ [~alms_@209-6-130-32.c3-0.bkl-ubr1.sbo-bkl.ma.cable.rcn.com] has joined #ccl
14:20:21 rme [~rme@50.43.184.114] has joined #ccl
14:47:22 krrrcks [~dbr@109.46.164.218] has joined #ccl
14:47:59 hi! has somebody used ccl together with postmodern on windows?
14:48:22 i got the problem of "bad message length" and I suppose it is something like line endings, encodings or something that is not working properly.
14:49:17 krrrcks: I haven't used Postmodern, but I am on Windows. I can test on my system if you like. What's your setup?
14:52:14 postgresql v 9.1.3 local or postgresql via tcp/ip on a different box. march distribution of quicklisp.
14:53:02 (progn (ql:quickload "postmodern") (require 'postmodern) (postmodern:connect-toplevel "database" "user" "password" "host"))
14:53:22 everything works and I see the user on the pgadmin3 tool
14:53:36 then a simple (postmodern:query "select 10") fails.
14:54:52 http://lists.common-lisp.net/pipermail/postmodern-devel/2012-March/001004.html
14:54:55 there are the details.
14:58:46 -!- billstclair [~billstcla@unaffiliated/billstclair] has quit [Quit: Linkinus - http://linkinus.com]
14:59:09 billstclair [~billstcla@p-68-237-140-116.dsl1.rtr.chat.fpma.frpt.net] has joined #ccl
14:59:09 -!- billstclair [~billstcla@p-68-237-140-116.dsl1.rtr.chat.fpma.frpt.net] has quit [Changing host]
14:59:09 billstclair [~billstcla@unaffiliated/billstclair] has joined #ccl
15:04:02 Looking.
15:04:14 Thx. That's great!
15:04:16 I have a slightly older version of PostgreSQL installed already, but that shouldn't matter.
15:04:36 if it's >8.1 or something should be working.
15:04:48 Yeah, 9.0
15:05:14 I suppose there is some encoding problems with the standard settings. I fiddled a bit with DEFAULT-ENCODING and those CCL variables but didn't find a way to get it working.
15:05:43 On Lispworks it is known to run under Windows (on the postmodern mailinglist). Yesterday I tested with the SBCL fork for Win32 and it worked out of the box as well.
15:06:56 krrrcks: have you tried specifying the line-ending options?
15:07:16 I testedt it with :unix
15:07:26 that was the setting I found on my linux box.
15:08:06 I could try with :windows ... let's see. I am not sure if I did that yesterday.
15:10:39 with :windows same error
15:14:14 I'll do some testing but stay on this channel.
15:15:39 OK, got it working here.
15:15:44 Didn't get your error.
15:18:30 ah.
15:18:32 interesting.
15:18:37 what CCL version?
15:18:55 what value for CCL:*DEFAULT-EXTERNAL-FORMAT*
15:19:17 krrrcks: http://paste.lisp.org/display/128335
15:19:59 krrrcks: :UNIX
15:20:01 Wonderful! :)
15:20:02 krrrcks: oddly.
15:20:13 It's working at your place but not at mine.
15:20:40 Also
15:20:59 My encoding in the db I tested with is UTF8
15:21:13 i was using 1.7-dev-r14645M
15:21:16 mine as well.
15:21:28 and i started ccl with -k UTF8
15:22:31 http://paste.lisp.org/display/128336
15:24:19 same here. only LC**something* is German, Germany.
15:24:22 strange.
15:25:14 well... perhaps I should test it with the same ccl version. I can do that later. But veeeeery strange.
15:25:28 Indeed.
15:25:28 I am still thinking about an encoding problem.
15:25:33 Seems likely.
15:26:05 krrrcks: 1.7-dev-r14645M is a rather old trunk ccl, so updating ccl is probably a good idea.
15:27:42 You could always run Wireshark or tcpdump and capture packets for when you test against the remote, networked PgSQL server and see if there's odd encoded commands flying across the wire.
15:28:01 Might be an easy way to confirm or refute that hypothesis.
15:35:26 yeah. i'll do an ccl upgrade later and tell you about the results. thanks for your help!!
15:38:54 krrrcks: You're welcome =] Happy to be helpful.
16:06:08 -!- jdz [~jdz@193.206.22.97] has quit [Ping timeout: 246 seconds]
17:45:08 hmmm... i now use the same CCL version as dnm but I still get that error... :/
17:57:05 krrrcks: Are you running into the problem in http://trac.clozure.com/ccl/ticket/899 ? If you've updated, please be sure you've done (rebuild-ccl :clean t) to build an updated heap image.
18:07:12 ah. yeah, looks similar to that ticket #899
18:13:25 when i use the test case written there I get a #(38) from that defun FOO as well.
18:14:43 does that mean I need the newest development version as the bug appears in the 32 bit version of 1.7-r14925M (which is what I just downloaeded from the ccl homepage)?
18:16:36 Did you get the lisp by downloading it via svn? Or did you get a zip file?
18:18:44 I got the zip file.
18:19:00 Because dma used that version as well.... but it was the X86_64 ;) *G*
18:19:21 Do you have Subversion installed on your machine?
18:19:40 yeah. no problem.
18:21:30 OK. Go to your ccl directory and run svn up. Then run wx86cl.exe and evaluate (rebuild-ccl :clean t). That'll build a new heap image that includes the fix for ticket:899.
18:40:58 okay. i'll give it a try.
18:47:16 hm. i've done the REBUILD-CCL and am now running 1.7-r15251M but the error is still there. :/
18:47:17 strange.
18:53:23 -!- pbgc [~pbgc@bl20-175-98.dsl.telepac.pt] has quit [Quit: Textual IRC Client: http://www.textualapp.com/]
18:53:41 I am running out of ideas ... :(
18:54:35 I'll see if I can get ccl and postmodern working on 32-bit Windows.
18:55:37 rme: I had no issues here.
18:55:58 dnm: Did you run it on 32 or 64 bit?
18:56:23 Windows 7 64-bit, PostgreSQL 9.0 64-bit, and CCL 1.7 64-bit
18:56:44 (not that I think the bit-ness of CCL or PgSQL should matter...)
18:57:05 as I understood the ticket 899 was on 32 bit only?
18:58:14 (I mean: CCL 64-bit may matter if the 32-bit version is somehow broken, but I don't think the connection or suspected encoding issue, if any, is between any bit-ness mismatch between the CCL binary and the PgSQL binary; I seem to recall you had a 32-bit PgSQL install in your situation?)
18:58:48 dnm: there was a compiler bug that affected 32-bit targets.
18:58:54 Are they any Postmodern debug settings to see what it's marshalling on the wire in the PgSQL wire format?
18:59:08 ticket 889 is fixed in my ccl. i get the right number in the test case.
18:59:24 rme: Ah, didn't know that. For 1.7 release?
18:59:33 krrrcks: Then what error do you get now?
19:00:33 it is still the "Database error: onb #: Das Geraet erkennt den Befeh l nicht. (error #22) during write [Condition of type CL-POSTGRES:DATABASE-SOCKET-ERROR]
19:00:37 and the connection is lost.
19:00:46 krrrcks: be sure to recompile everything
19:01:17 ok. that may be the problem. just a second.
19:03:56 Yeah!
19:03:59 Now it works! :)
19:04:18 *krrrcks* jumps around and hugs dnm and rme.
19:04:21 Woo hoo!
19:04:25 Congrats!
19:04:36 So it was the 899 ticket on win32.
19:04:39 good to know.
19:04:46 I post that on the postmodern mailing list.
19:04:47 krrrcks: Do you have a URL to that Trac ticket?
19:04:59 http://trac.clozure.com/ccl/ticket/899
19:05:02 I didn't even know about that bug.
19:05:05 Thanks!
19:05:18 Me either. But rme was aware of that. Thankfully.
19:05:35 Indeed. Thanks rme!
19:06:28 Fortunately, I'll be making a 1.8 release Real Soon Now, and it will include the fix for #899 in the binaries.
19:06:41 krrrcks: Thanks for pointing me towards Postmodern, I hadn't heard of it before. Seems like a nice library!, and one I can use in some other PgSQL/DB projects.
19:07:29 krrrcks: You have me curious now, what are you looking to do with Postmodern and PgSQL yourself?
19:07:48 yes, it looks nice and has some nice features. but I am just starting using it.
19:08:03 well, it is for a web application where I save the data in a postgresql database.
19:08:12 until know i was using CLSQL but was not very happy with it.
19:08:20 it worked ... somehow sometimes. :) *G*
19:08:35 Ah hah! rme did run tcpdump back 3 mos. ago to discover it *was* sending bad bytes on the wire:
19:08:39 "At first it looks like a bug in the library, but tcpdump reveals mangled data in which the length of simple-describe-message packet is declared incorrectly as 1. This four byte length value in the packet's header is computed through define-message macro in postmodern/cl-postgres/messages.lisp."
19:09:13 But s/he also did more digging into CCL guts as well.
19:09:56 krrrcks: Heh, indeed. I found some PostGIS related CL code as well, linked from the Postmodern page, so I'm playing with that now as well. Thanks again!
19:12:18 Yeah, looks like a nice library. Happy hacking! :) *G*
19:13:00 Or I guess maybe emit did that tcpdump. Didn't read the ticket close enough. Still, good to know.
19:13:03 krrrcks: You too!
19:14:53 yeah, my colleagues who are using Windows will be happy that they can test with the environment they are used to and my customer hopefully will be happy with the final application ;) (that will run under linux).
21:36:40 -!- krrrcks [~dbr@109.46.164.218] has quit [Quit: WeeChat 0.3.0]
22:52:35 -!- milanj [~milanj_@178-223-128-113.dynamic.isp.telekom.rs] has quit [Quit: Leaving]