Your code looks correct to me, I can't imagine why there'd be a problem.
I've never used (or even heard of) a pervasive database, but if you can
write JDBC code that works against it, it ought to work in ESQL.

Is your pool set up correctly?  Do you log in with the same user as in your
separate JDBC test?  Can you tell from the generated java source if it is
following the same steps you do in your own JDBC?

If you put code in an <esql:no-results> block after the <esql:results>
block, does that execute?

Just out of curiosity, what does the
<esql:use-limit-clause>pervasive</esql:use-limit-clause> line do?

-Christopher




|---------+---------------------------->
|         |           Leszek Gawron    |
|         |           <[EMAIL PROTECTED]>  |
|         |                            |
|         |           10/30/2003 06:00 |
|         |           AM               |
|         |           Please respond to|
|         |           users            |
|         |                            |
|---------+---------------------------->
  
>--------------------------------------------------------------------------------------------------------------|
  |                                                                                    
                          |
  |       To:       [EMAIL PROTECTED]                                                  
                    |
  |       cc:                                                                          
                          |
  |       Subject:  ESQL problem                                                       
                          |
  
>--------------------------------------------------------------------------------------------------------------|





I have encountered something strange concerning ESQL. I am using Pervasive
database. This is a ESQL code snippet:
<esql:connection>
    <esql:pool>symfonia</esql:pool>
    <esql:execute-query>
        <esql:use-limit-clause>pervasive</esql:use-limit-clause>
        <esql:query>select * from xt where kod like  '%ń%'</esql:query>
        <esql:results>
            <esql:row-results>
                <row>
                    <esql:get-columns/>
                    <xsp:logic>
                        String test = <esql:get-string column="kod"/>;
                        getLogger().error( test );
                    </xsp:logic>
                </row>
            </esql:row-results>
        </esql:results>
    </esql:execute-query>
</esql:connection>

If you have a strange character in select statement - that's OK - it's a
polish letter.
The problem is: the query does not output any data.

The same written in JDBC (off cocoon):

PreparedStatement stmt = conn.prepareStatement("select * from xt where kod
like '%ń%'");
stmt.execute();

ResultSet rs = stmt.getResultSet();

while ( rs.next() ) {
             System.out.println( rs.getString( "kod" ) );
}

works just fine.

I have checked the xsp java generated source - the polish letter is
encoding
using the same byte value so I do not get it what makes the difference.

Comments anyone ?
             lg


--
            __
         | /  \ |        Leszek Gawron            //  \\
        \_\\  //_/       [EMAIL PROTECTED]           _\\()//_
         .'/()\'.     Phone: +48(501)720812     / //  \\ \
          \\  //  recursive: adj; see recursive  | \__/ |


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to