RE: [Squirrel-sql-users] SQuirrel not supporting some Mckoi SQL c ommands.

[Colin B. <Col...@as...>]

Hi Mamading,

I suppose I should thank you for making me install Mckoi <grin/>. Its been
on my todo list for a while but I just haven't gotten around to it.

I've noticed is the SQuirreL isn't handling the LONGVARCHAR data type
correctly. Mckoi uses this to represent column and table names etc. We'll
fix this in the next release and this should fix most (if not all of your
problems.

Col



-----Original Message-----
From: Mamading Ceesay [mailto:mc...@ev...]
Sent: Monday, 11 March 2002 7:13
To: squ...@li...
Subject: [Squirrel-sql-users] SQuirrel not supporting some Mckoi SQL
commands.


As part of the SQL syntax supported by the Mckoi SQL 
Database, the following commands are available:

--------------------------------------------------

14. DESCRIBE syntax 

DESCRIBE table_name

This command provides information about the columns 
of the table. It shows the column names, the type / 
size and scale (if applicable) and other useful 
information. 

15. SHOW syntax 

SHOW engine_variable [ WHERE search_expression ]


engine_variable ::= TABLES | SCHEMA | STATUS | CONNECTIONS

Shows internal information about the database system. 
SHOW TABLES returns a list of tables in the database. 
SHOW STATUS returns debugging and statistical 
information about the internal state of the database 
engine. SHOW CONNECTIONS returns a snapshot of the 
current connections on the database. SHOW SCHEMA 
lists all the schema defined. 

The SHOW syntax has an optional WHERE clause that 
can be used to filter the result. For example, the 
following statement returns a list of all tables 
which start with the letter 'A'. 

SHOW TABLES WHERE table_name LIKE 'A%'

------------------------------------------------

Having just tried using these commands from SQuirreL 
connected to an embedded Mckoi database, the only one 
of the above commands that actually worked properly 
was the SHOW SCHEMA command.

Any ideas as to why this might be the case and how 
the other commands can be made to work from SQuirreL?

I realize that I can obtain the same information 
provided by these commands by using the Objects tab, 
but it seems to me that SQuirreL should support all 
the SQL commands provided by the underlying database, 
where possible.

Further investigation reveals problems with the Objects
tab as well, specifically the Columns subtab.  the 
COLUMN_NAME column is filled with <unknown>, as is the 
TYPE_NAME column amongst others.

Hmmm!  I suspect the problems with the SQL commands 
and the Columns subtab share the same underlying cause.

Thoughts?

Regards,
Mamading Ceesay

"Don't worry about what anybody else is going to do. 
The best way to predict the future is to invent it."

-- Alan Kay



_______________________________________________
Squirrel-sql-users mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users