Desmond O. Chang | 9 May 2008 15:41
Picon
Gravatar

*default-database-type*'s problem and patch

Hi,

When I eval (create-database '(...)) without specifying :database-type,
I got a condition like following:

There is no applicable method for the generic function
 #<STANDARD-GENERIC-FUNCTION CLSQL-SYS:DATABASE-CREATE (1)>
when called with arguments
 ((NIL "test4" "root" "touch724831") NIL).
  [Condition of type SIMPLE-ERROR]

I checked clsql's code and found the default value of database-type
in create-database, destroy-database, probe-database and
list-database are nil.

It doesn't conform to the document. I think the default values
should be *default-database-type*.

The attachment is my patch.

Thanks,
Desmond
Attachment (default.patch): text/x-diff, 1758 bytes
_______________________________________________
CLSQL mailing list
CLSQL@...
http://lists.b9.com/cgi-bin/mailman/listinfo/clsql
(Continue reading)

Jan Rychter | 11 May 2008 12:37
Gravatar

Are join slots read-only?

Are CLSQL join slots (:db-type :join) intended to only retrieve
relationships?

I was rather puzzled when I tried setf on a join slot and got nothing in
the database. Either of the following has to be true:

1. I haven't read the documentation carefully enough and I'm just asking
silly FAQs.

2. The documentations and examples do not show it, but the functionality
is there. I just don't know how to use it.

3. Functionality isn't there and it's waiting for someone to implement
it.

4. It is impossible to implement it.

I'm tending towards (3).

How do people deal with updating relations with CLSQL? Do you manage
them manually? Do you specify :writers on join slots? Any other
solutions?

--J.
Ross Hall | 14 May 2008 23:36
Picon

unit tests for time.lisp

Hello,

I have created some unit tests for the time.lisp file.
Is there a preferred format or manner in which I should submit the
tests I created?

Thank you,
Ross
Kevin Rosenberg | 15 May 2008 01:30
Favicon

Re: unit tests for time.lisp

Ross Hall wrote:
> I have created some unit tests for the time.lisp file.

Thank you. Unit tests are very nice to receive.

> Is there a preferred format or manner in which I should submit the
> tests I created?

Unified diff would be the best way. I imagine the changes are likely
limited to the tests/tests-time.lisp file.

Kevin
Ross Hall | 20 May 2008 18:40
Picon

Re: unit tests for time.lisp

Hello,

I am sorry it took me so long to get around to sending you the diffs.
The tests are in tests/tests-time.lisp and I added a macro
'assert-error' into tests/util.lisp

Both are attached.

Thank you,
Ross

On Wed, May 14, 2008 at 6:30 PM, Kevin Rosenberg <kevin@...> wrote:
> Ross Hall wrote:
>> I have created some unit tests for the time.lisp file.
>
> Thank you. Unit tests are very nice to receive.
>
>> Is there a preferred format or manner in which I should submit the
>> tests I created?
>
> Unified diff would be the best way. I imagine the changes are likely
> limited to the tests/tests-time.lisp file.
>
> Kevin
>
Attachment (time.diff): text/x-patch, 20 KiB
Attachment (utils.diff): text/x-patch, 358 bytes
_______________________________________________
(Continue reading)

Sabra Crolleton | 26 May 2008 04:05
Picon

Naming Conventions?

Does anyone have any naming conventions they would care to share? (For
models, slots, etc?). I'm looking to standardize my own projects as
the naming seems to be getting rather ad hoc.

Sabra
--

-- 
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.

Gmane