alias et tab issues SA 4.7

hi,

i'm using the latest version of SA (4.7 trial), i've found some minors issues :

1 / for some reasons, when i run a query (oracle 9i) without an alias it crashes scintilla (latest release 2.1). this not happen everytime, i noticed it happens when it's a table (public synonym : ok)

2/ when i choose "TAB" in the items selection key. this is what happened :

	Code:
	select * from ta[press tab]

gives me

	Code:
	select * from tatable

instead of

	Code:
	select * from table

No particular problem with the key "ENTER", it works perfectly.

Not a big deal, maybe these are known issues.

i'm french so google help me a lot to express myself, sorry...:)

Sai

Hi.

Which specific SQL editor/version are you using? Which version of Oracle OCI are you using for db connections?

hi,

	Quote:
	SQL editor/version

Scite / 2.01

	Quote:
	Oracle OCI

Oracle9i Enterprise Edition Release 9.2.0.7.0

Thanks for your help.

Sorry, I will not be able to help you with Scite, we don't have it here and I cannot check it There might be some compatibility issue. Please try using a different editor.

As for the table / alias issue, I doubt it is caused by a table or alias reference. It is likely caused the way the data is returned, some unsupported data type, like an object or nested table, etc...is leading to an error during data retrieval which is leading an unhandled exception and in turn to a crash Try it with different tables, for example, SELECT sysdate FROM dual; Also please check your ORANET.LOG file, there could be a reference to some specific Oracle error. If we know that error, we could figure out how to fix or to workaround it.

One other possible solution is to use ODBC or ADO.NET based connection instead of OCI, Maybe that will help to avoid crashes caused by data retrieval

	Quote:
	One other possible solution is to use ODBC or ADO.NET based connection instead of OCI, Maybe that will help to avoid crashes caused by data retrieval

I tried to use ODBC driver, it crashed anyway.

	Quote:
	It is likely caused the way the data is returned, some unsupported data type, like an object or nested table, etc...is leading to an error during data retrieval which is leading an unhandled exception and in turn to a crash Try it with different tables

The bug occurs randomly on a specific table. All other tables dont bug.
But sometime this specific table displays results...and sometime it bugs.

	Quote:
	Also please check your ORANET.LOG file

I cant find it anywhere, it's supposed to be in the oracle directory ?

Thank for the time,
Sai

Please post column definitions for that particular table, or better the complete DDL for the table so I can try to reproduce it locally.

How many records do you retrieve from that table when it crashes? Is that always a small number (hmm... less than 10000 records)?

Sorry, I meant to refer to SQLNET.ORA file and that should be in the application working directory

	Quote:
	Please post column definitions for that particular table, or better the complete DDL for the table so I can try to reproduce it locally.

	Code:
	Nom NULL Type ------------------------------ -------- ------------------- NUMCOMMAND VARCHAR2(9) COMMANDOBJECTIDEN VARCHAR2(3)

I created this table from another table like this

	Code:
	create table TABLE_XXXX as select * from TABLE_YYYY

	Quote:
	How many records do you retrieve from that table when it crashes? Is that always a small number (hmm... less than 10000 records)?

about a hundred rows...

	Quote:
	Sorry, I meant to refer to SQLNET.ORA file and that should be in the application working directory

I found it but there is nothing relevant i think i post it anyway

Code:

#############################################################################
# #
# SQLNET.ORA #
# QAC EPASI 2.0 #
# MSC - *********** #
# #
# #
# #
#############################################################################

names.default_domain = world

names.directory_path= (TNSNAMES,ONAMES,HOSTNAME )

Sqlnet.authentication_services=NONE

names.default_domain = *****
name.default_zone = *****

I cannot reproduce this issue with Notepad, with DB Tools and with PL/SQL Developer. I haven't tried Scintilla based editors, but I don't think the issue it editor specific. Are you sure the issue is specific to one particular table. I think it is an issue with unstable database connection. Can you try other tables to find out whether it is table specific or connection specific? Also, please check which SQL Assistant popups are invoked before you use the Execute SQL Code function. Maybe this happens when certain functions are invoked in a certain sequence.

You're right it's not specific to scite i tried with notepad i've got the same bug : it crashed the editor...

the query works fine with others editor like Toad or SqlDeveloper (without SA)...

	Code:
	Also, please check which SQL Assistant popups are invoked before you use the Execute SQL Code function. Maybe this happens when certain functions are invoked in a certain sequence.

i notices it happen just after the popup "connection context" if i run the query before its display i get the results. after i get an error and the editor vanishes

EDIT : Yes i'm sure it's specific to 2 tables that i creates the same way, only theses 2 tables...

Let's try to disable the automatic syntax checking feature and verify if that helps.