cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Myers <>
Subject Re: ESQL retake
Date Mon, 01 Apr 2002 16:36:56 GMT
Hi Elias,

Instead of replying to your mail, i'll reply to your readme.

> the inherent complexity of a system that's built on patches and
> suggestions for almost 3 years now (DB: flame me later :-). Take a look at
That may be a good thing.  We'll see.

=> no aggregates! what's the use in groups without aggregate functions ?!
i'm not sure this justifies a complete rewrite.

> 1)...
> 2) then, I map schema types to xsl templates.
of course.  Nice schema, by the way.

>3) finally, I try to define the needs of the helper class and move as much
> code away from the logicsheet as possible.
These will hopefully fall into place for you.

> My initial target is to make this implementation of ESQL 100% compatible 

> with the current logicsheet. However, I obsoleted the usage of
> <esql:get(datatype)/> tags because it's meaningless to map JDBC datatypes
> to a weakly-typed environment such as XML text nodes.

1) backward compatibility: how big an issue?
If you use a different namespace, it can be none.

2) multiple connections per logicsheet: would we be needing them? 
nested queries:
 oh yes. OT: wanna see something cool?  see attached: messageboard.xsp.

multiple connections:
 why not? they are no harder than nested queries.  See how they are done now.
I think it is beautiful.

Version history:
0.01: basic functionality, compiles and executes esql example page

what i want to know is,
is it going to fix your original problem?

I did some more thinking about it.  What are you using as your odbc-jdbc bridge?  I spent
about a day trying to get esql to work in jdk 1.4 because it has a jdbc2 compliant bridge
driver.  For production work, i use mysql and the gpl'd mysql driver.

I couldn't figure out why it was acting like you were getting an exception, and
 not printing the stack trace for you.  There are a couple of cases where the 
current esql logicsheet will swallow exceptions.  One corner my grouping code 
cuts is always doing a resultSet.getString and a string comparison no matter
what the column type really is.  Some jdbc drivers might not take kindly to
that. I'm not sure.

will your code allow nested groups?
one of my considerations was arbitrary nesting.


View raw message