I guess practicing with ejb 1.1 is OK for learning purposes.  When you
start deploying "production" EJBs you'll need to go with ejb 2.0 for
performance.

Craig B.:  Are you planning an updated big red EJB book that includes
design patterns and performance?

---------- Forwarded message ----------
Date: Tue, 24 Sep 2002 13:10:37 -0700 (PDT)
From: Mitch J. Chan <mjchan@e...>
Reply-To: Enterprise Java Beans <enterprise_java_beans@p...>
To: Enterprise Java Beans <enterprise_java_beans@p...>
Subject: [enterprise_java_beans] Re: I can't see Cloudscape tables created
    via CMP Entity beans deployment

I got this off the site:


http://java.sun.com/j2ee/tutorial/1_3-fcs/doc/Tools4.html


  Because the table names in these SQL statements are case sensitive, you
  must enclose them in double quotes: 

  ij> select * from "TeamBeanTable


Try the following:

  ij> select * from "TaxEJBTable";


I'm assuming that the SQL you entered during the bean deployment matches
the query above.

Craig B:  What's you're take?  Is this a case sensitivity issue?

-Mitch


On Tue, 24 Sep
2002 santiago.molina@m...
wrote:

> Yes, I can see the table when I write
> select * from sys.systables;
> 
> but I can't do select * from TAXEJBTABLE;
> 
> > You can view the existing tables using the command
> 
> 	select * from sys.systables;
> 
> On Mon, 23 Sep 2002 santiago.molina@m... wrote:
> 
> > > > I can create the tables via deployment, I also can see them in the 
> > d> > atabase catalogue but I can't query them from isql (I got the error
> > E> > RROR 42X05: Table 'TAXEJBTABLE' does not exist)
> > 
> > > > Does anyone know something about this?
> > 
> > > You don't say which server you're using (although it looks like it 
> could 
> > be
> > t> he RI) but I've experienced that the table names include the quotes, 
> > such
> > t> hat you need to query 'TAXEJBTABLE' and not just TAXEJBTABLE
> > 
> > thanks for your answer.
> > The database server is Cloudscape and the application server is RI. I've 
> > already tested 'TAXEJBTABLE' and I get the same error.
> > 
> 
>