27 May 2005 06:04
Event based CLSQL?
Hi Does CLSQL (in particular clsql-postgresql-socket) support non-blocking sockets for use in event-based servers? -- -- Robert Marlow <bobstopper@...>
Hi Does CLSQL (in particular clsql-postgresql-socket) support non-blocking sockets for use in event-based servers? -- -- Robert Marlow <bobstopper@...>
Robert Marlow wrote: > Does CLSQL (in particular clsql-postgresql-socket) support non-blocking > sockets for use in event-based servers? Not that I'm aware of. If it does, it'd be completely coincidental. No attempt has been made to support event-based servers. -- -- Kevin Rosenberg kevin@...
Hello, Is it intentional that CONNECT doesn't accept paths, only strings? E.g. ;;;; *db-filename* is #p"/home/z0d/projects/quotes/database/quotes.db" (connect (list *db-filename*) :database-type :sqlite3) doesn't work, I get a type error. Thanks for your help. -- -- '(Yours parenthetically), peter barabas. ((call/cc call/cc) (call/cc call/cc))
Hello,
first, i apologize about my english :)
i have a littre problem with SBCL, CLSQL, ODBC to connect to a Microsoft
SQL SERVER 2000.
Configuration :
- Redhat fedora core 3
- SBCL 0.8.18
- unixODBC 2.2.9
- freeTDS 0.62.3
I have downloaded :
- rt-20040621
- uffi-1.4.37
- clsql-3.1.15
Under sbcl :
(require :asdf)
(push #P"/my-home-dir/rt-20040621/" asdf:*central-registry*)
(push #P"/my-home-dir/uffi-1.4.37/" asdf:*central-registry*)
(push #P"/my-home-dir/clsql-3.1.15/" asdf:*central-registry*)
(asdf:operate 'asdf:load-op 'clsql)
(clsql:connect '("ip-address-sql-server-2000" "login" "password")
:database-type :odbc)
Error message :
; loading system definition from
; #P"/my-home-dir/clsql-3.1.15/clsql-odbc.asd" into
(Continue reading)Peter BARABAS wrote: > Is it intentional that CONNECT doesn't accept paths, only strings? E.g. Yes, http://clsql.b9.com/manual/sqlite3.html#id2624768 states that the connection-spec requires a string. > ;;;; *db-filename* is #p"/home/z0d/projects/quotes/database/quotes.db" > (connect (list *db-filename*) :database-type :sqlite3) > doesn't work, I get a type error. That's to be expected. That said, it's likely that CLSQL could be extended to accept a pathname as well and the documentation updated to include this functionality. The ease of this extension will depend upon how much the connection-spec processing that is common amongst backends expects a string in that position. So, while pathnames may be a future extension, you're safest plan is to convert the pathname to a namestring so that current and future versions of CLSQL will work with your application. -- -- Kevin Rosenberg kevin@...
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | 31 |
RSS Feed3 | |
|---|---|
14 | |
5 | |
1 | |
4 | |
3 | |
1 | |
7 | |
9 | |
7 | |
3 | |
14 | |
3 | |
3 | |
1 | |
15 | |
10 | |
7 | |
12 | |
3 | |
8 | |
2 | |
7 | |
4 | |
6 | |
4 | |
8 | |
3 | |
6 | |
3 | |
11 | |
4 | |
1 | |
10 | |
40 | |
34 | |
20 | |
25 | |
7 | |
18 | |
15 | |
29 | |
8 | |
1 | |
4 | |
11 | |
16 | |
12 | |
8 | |
15 | |
14 | |
8 | |
11 | |
4 | |
2 | |
15 | |
17 | |
6 | |
6 | |
10 | |
4 | |
26 | |
26 | |
18 | |
8 | |
13 | |
34 | |
32 | |
20 | |
16 | |
12 | |
10 | |
29 | |
23 | |
11 | |
13 | |
16 | |
10 | |
19 | |
7 | |
26 | |
7 | |
21 | |
8 | |
21 | |
22 | |
8 | |
29 | |
22 | |
11 | |
7 | |
3 | |
11 | |
13 | |
12 | |
11 | |
3 | |
17 | |
35 | |
18 | |
15 | |
4 | |
13 | |
26 | |
3 | |
2 | |
3 | |
5 | |
5 | |
5 | |
1 | |
11 | |
15 | |
2 | |
5 | |
3 | |
59 |