|Re: DTP: Why SQL statements die saying "no database selected" [message #211266 is a reply to message #211225]
||Fri, 28 March 2008 11:01
| Lawrence Mandel
Registered: July 2009
I think you'll have more success with DTP questions on the DTP newsgroup.
Co-author Eclipse Web Tools Platform: Developing Java Web Applications
>I'm still working through my first Data Tools Platform use of MySQL. I
>had exactly the same problems with Derby--never resolved.
>I have set up and connected to a MySQL database which I've actually used
>successfully from a hand-deployed Java project. So, I know this database
>works, though here I'm using a different schema and table within it. The
>reason I switched to MySQL was that I couldn't get Derby to accept SQL
>statements, but had never used the latter before.
>At the following link, you see the illustration of my SQL statements,
>Data Source Explorer set-up of the MySQL database to which I'm connected.
> http://www.windofkeltia.com/j2ee/tut-images/mysql-database.j pg
>In the next link, you see the result of doing an Execute All with the
>error displayed as there being no database selected.
> http://www.windofkeltia.com/j2ee/tut-images/mysql-statement- failure.jpg
>Would this not simply be that I don't know what it means to "select" a
>database in DTP? I've tried several silly things like selecting various
>subicons in the Data Source Explorer view before doing an Execute All in
>the SQL statement window--all to no avail. I've been stumped here for
>Both Derby and MySQL have slain my knight before the gates of DTP
>success here. I need a knight who knows his way around this obstacle!
>A million thanks in advance!
Powered by FUDForum
. Page generated in 0.01593 seconds