You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2006/10/06 20:01:20 UTC
[jira] Updated: (DERBY-105) drop table statement shows wrong
message after dropping table
[ http://issues.apache.org/jira/browse/DERBY-105?page=all ]
Daniel John Debrunner updated DERBY-105:
----------------------------------------
Component/s: Tools
(was: SQL)
This is an ij tool issue, not a SQL langauge issue.
> drop table statement shows wrong message after dropping table
> -------------------------------------------------------------
>
> Key: DERBY-105
> URL: http://issues.apache.org/jira/browse/DERBY-105
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.0.2.2
> Environment: generic
> Reporter: Amit Handa
> Priority: Minor
>
> If we drop a table using the ij tool,
> it returns a message that "0 rows inserted/updated/deleted"
> giving an impression as if the table is still there and some update has been done
> (as if executed a DML statement) to the table, whereas this is not the case.
> Note that the same message appears while we execute a DML(insert/update/delete) query on the table.
> which further confuses the user as if a table hasn't been dropped and updations still happenning
> on the table instead of dropping(and creating)
> The same is the case when a table is created.
> Rather it when a table is created
> ij> create table temp(cv char(10));
> 0 rows inserted/updated/deleted <-- Wrong message
> ij> select * from temp;
> CV
> ----------
> 0 rows selected
> ij> insert into temp values('a');
> 1 row inserted/updated/deleted
> ij> drop table temp;
> 0 rows inserted/updated/deleted <-- Wrong message
> ij>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira