Dear Team,
At the moment, as Ian has mentioned, the next major release is
dependent on the porting of a big chunk of new functionality that he has
written to the CL-SQL and Postmodern backends. I think it is worth a
status report on that.
I have spent a total of 24 hours of work
Just FYI - the query language is pretty primitive at present although
Daniel has expressed some interest in expanding on the current sketch.
Ian
On May 3, 2008, at 11:40 AM, Leslie P. Polzer wrote:
IE> but we haven't had any work done on this in Postmodern yet.
by the way, are there any p
> IE> but we haven't had any work done on this in Postmodern yet.
>
> by the way, are there any people waiting for postmodern being ported, or is
> it causing any problems if it's not ported yet (i.e. delaying release or
> something)?
I'm waiting for unstable because of the query language, the c
Hi Alex,
You make a good point below. I haven't dealt with these kind of small
subsets from large sets using multiple parameters problems in a large
system. However, if we take a page from Robert's book about using
lisp as the query engine - how would we solve this problem just with
lis
Thanks Alex.
The ports of CL-SQL and Postmodern are the primary things holding up
the release process right now. If there are major issues there, I may
have to refactor my implementation. It would be really helpful to get
an ETA on a port and get the main and unstable branches integrated.
IE> but we haven't had any work done on this in Postmodern yet.
by the way, are there any people waiting for postmodern being ported, or is
it causing any problems if it's not ported yet (i.e. delaying release or
something)?
because for now projects i'm working on seem to be working more-or-l
??>> this cache mode (and postmodern backend in general) is oriented on
??>> webserver-like workload -- each web request always is wrapped into
??>> transaction. if request does no DB activity, that's OK -- starting txn
??>> overhead is not that significant on scale of typical HTTP request
??>> ti
Definitely work elephant-unstable if you want to test the new
functionality. Most of the activity in the main branch has been in
and around the postmodern interface. The limiting factor in merging
the branches is getting support for the new data store API (i.e. for
btrees w/ duplicate key
> this cache mode (and postmodern backend in general) is oriented on
> webserver-like workload -- each web request always is wrapped into
> transaction. if request does no DB activity, that's OK -- starting txn
> overhead is not that significant on scale of typical HTTP request time. but
> many re
??>> but if you do not start your transactions explicitly, enclosing as
??>> many operations as posible, global-sync-cache absolutely makes no
??>> sense -- it takes more effort to synchornize changes than to actually
??>> load value from database, if that's just a single value. so, maybe, if
??>>
Dear Alex,
> it seems you didn't wrap your code into explicit transaction.
Thanks for your quick analysis.
> but if you do not start your transactions explicitly, enclosing as many
> operations as posible, global-sync-cache absolutely makes no sense -- it
> takes more effort to synchornize cha
??>> can you catch a backtrace? it seems to be quite relevant here
LPP> 6: (LAMBDA NIL)
LPP> At
LPP> /home/sky/projects/mystic/hg.beta1/packages/elephant/src/db-postmodern
LPP> /pm-sql.lisp:1577: (LAMBDA NIL)
LPP> At
LPP> /home/sky/projects/mystic/hg.beta1/packages/elephant/src/db-postmo
Marc wrote:
Ian Eslick wrote:
Great! Actually in writing the following e-mail, I realized that
this had forced me to think through a bunch of things and so I wrote
a version of the functionality in associations.lisp and just checked
it in.
Start playing with, reading and commenting on what'
> LPP> With this enabled I sometimes get
>
> LPP> Database error 55000: currval of sequence "txn_id" is not yet LPP>
> defined
in this session
>
> can you catch a backtrace? it seems to be quite relevant here
6: (LAMBDA NIL)
At
/home/sky/projects/mystic/hg.beta1/packages/elephant/src/d
14 matches
Mail list logo
