On 05/05/2013 10:45 PM, John Gateley wrote:
Lots of newbie questions:
1) If I am creating a new class that has a "size" field, what is the
convention for naming the initialization argument? "size" doesn't
work! This name must be known by all class creators.
(class object %
(init init-size) ;;
Here're some answers to a subset of your questions:
On 2013-05-05 21:45:20 -0500, John Gateley wrote:
> 1) If I am creating a new class that has a "size" field, what is the
> convention for naming the initialization argument? "size" doesn't
> work! This name must be known by all class creators.
>
Lots of newbie questions:
1) If I am creating a new class that has a "size" field, what is the
convention for naming the initialization argument? "size" doesn't
work! This name must be known by all class creators.
(class object %
(init init-size) ;; init-size cannot be size
(define size init-
It looks like postgres is expecting an integer instead of a timestamp
for that query parameter. Are you sure the corresponding field is
declared as a timestamp? Make sure you've written things in the right order.
Ryan
On 05/05/2013 09:39 PM, Kejia柯嘉 wrote:
Hi Ryan,
Thanks a lot for your repl
Hi Ryan,
Thanks a lot for your reply.
How should I `insert into' a timestamp field in postgres? When I apply
a sql-timestamp to query-exec, I got exceptions:
``
query-exec: cannot convert given value to SQL type
given: (sql-timestamp 2013 5 5 21 56 22 48000 #f)
type: int2
expected: int1
On 05/04/2013 01:22 PM, Kejia柯嘉 wrote:
Hi,
How should I construct a postgresql timestamp in terms of current time?
Thanks.
On the Racket side:
(require db db/util/datetime (prefix-in srfi: srfi/19))
(srfi-date->sql-timestamp-tz (srfi:current-date))
On the server side:
(define c (post
Version 1 was what I meant by not duplicating work, and version 2
seems much too complicated.
It looks like syntax/parse/experimental/eh, does what I need.
On Sun, May 5, 2013 at 1:11 PM, J. Ian Johnson wrote:
> One way is to have your ~or form in an ~and with a catch-all where you can
> observ
One way is to have your ~or form in an ~and with a catch-all where you can
observe the ordering.
That is,
(~and (~seq forms ...) (~seq (~or (~optional (~seq #:kw0 kw0)) ...others...)
...))
Then walk through (forms ...) when you're outputting your changed keyword
arguments to determine which to o
I'm trying to improve the struct: form in TR, and one of the things I
need to do is match a sequence of keyworded expressions, add
annotations on the expressions, and then put them back into the same
order.
I can either do a large ~or clause and have optional constraints on
each clause, but If I d
> In the context of packages, does it make sense to refer to a package
> name without a major version number, given that major versions are
> incompatible?
>
> I think the reasons we have to refer to package names would all require
> a major version, and so I agree with the way the current design s
At Thu, 2 May 2013 10:20:09 -0400, Walter Tetzner wrote:
> On Tue, Apr 30, 2013 at 12:24 PM, Matthew Flatt wrote:
> > 2. It could mean that the package system has a built-in way to declare
> > dependencies not only on a particular package, but on a particular
> > revision of a package ---
The docs for web-server/dispatch allude to the filesystem server that lurks
behind the dispatch rules to handle requests that are not handled by
dispatch rules.
Is there a way to explicitly send a request to the filesystem server?
For instance, I have a dispatch route that checks if the requested
12 matches
Mail list logo
