[This topic is migrated from our old forums. The original author name has been removed]
Hi ... Having weird issues with Auto Completion feature... Sometimes it works, and most of the time it doesnt..
Consider this:
*select g.sales_channel_cd*
*from gtr_sales_channel g*
First I typed select and the from parts, then gave alias to the table, then went back to my select part and typed g. followed by Ctrl+Space.. Auto complete popped up. Great! . Now i needed to continue and do some concatenation :
*select g.sales_channel_cd || ' ' || {color:#3366ff}g.sales_channel_touch*
*{color}from gtr_sales_channel g*
The Auto Completion did not work the second time I typed g. followed by Ctrl+Space to add sales_channel_touch field...
Version: DbVisualizer Pro 9.1 [Build #2050]
OS: Windows XP
OS Version: 5.1
OS Arch: x86
Java Version: 1.6.0_43
Java VM Name: Java HotSpot(TM) Client VM
Java VM Vendor: Sun Microsystems Inc.
Look and Feel: SyntheticaStandardLookAndFeel
Re: Auto Completion ... is not always completing..
Hi Alex,
Please give a detailed example of what does not work, and please do that in a new thread so we can better track the issues.
Best Regards,
Hans
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Auto Completion ... is not always completing..
Looks like the same issue to me -- autocomplete is not functioning properly. Just different scenarios to reproduce the same issue :) :p
Edited by: AlexML on Nov 22, 2013 3:04 PM
Roger Bjärevall
said
over 10 years ago
[This reply is migrated from our old forums.]
Re: Auto Completion ... is not always completing..
Alex,
One of your issues reported in this thread is fixed by 9.1.3. I suggest you split new posts into separate threads to better track what is what.
Regards
Roger
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Auto Completion ... is not always completing..
Roger
I do not think so.. Unless i manually change schema to dbo, the problem still persists... ...
Product: DbVisualizer Pro 9.1.3
Build: #2091 (2013/11/22 16:43)
Java VM: Java HotSpot(TM) Client VM
Java Version: 1.6.0_51
Java Vendor: Sun Microsystems Inc.
OS Name: Windows 7
OS Arch: x86
OS Version: 6.1
Roger Bjärevall
said
over 10 years ago
[This reply is migrated from our old forums.]
Re: Auto Completion ... is not always completing..
Alex,
This is now fixed in the 9.1.3 version.
http://www.dbvis.com/download/
Regards
Roger
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Auto Completion ... is not always completing..
Could it be the Schema is not dbo? Should the list of tables come from dbo schema?..
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed] [Attachment has been removed.]
Re: Auto Completion ... is not always completing..
Connected to a Sybase db..
select *
from
and hit Ctrl+Space
Nothing comes up, debug output below
08:42:45 [DEBUG ExecutorRunner-pool-2-thread-134 N.?] DbConnection='SYBAMR_FDA_PRD_DS01 PROD (PRIMARY fda_etma_prd)' Catalog='FDA_PRD_NY' Schema='fda_etma_prd' Table='null' Type(s)='null'
08:42:45 [DEBUG pool-3-thread-234 E.?] RootConnection: SybDatabaseMetaData.getTables("FDA_PRD_NY", "fda_etma_prd", "%", null)
Product: DbVisualizer Pro 9.1.2
Build: #2070 (2013/10/27 14:32)
Java VM: Java HotSpot(TM) Client VM
Java Version: 1.6.0_51
Java Vendor: Sun Microsystems Inc.
OS Name: Windows 7
OS Arch: x86
OS Version: 6.1
Roger Bjärevall
said
over 10 years ago
[This reply is migrated from our old forums.]
Re: Auto Completion ... is not always completing..
Alex,
Please share the details.
Regards
Roger
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Auto Completion ... is not always completing..
Just fyi -- it is still not functioning properly in many scenarios......
Hans Bergsten
said
over 10 years ago
[This reply is migrated from our old forums.]
Re: Auto Completion ... is not always completing..
Hi Alex,
As a temporary work-around:
1) Open Tools->Tool Properties,
2) Under the Database tab, expand the Sybase ASE node and select the SQL Statements node,
3) Select the SELECT ALL entry in the list and change its template to:
SELECT * FROM $$catalog$$$$catalogseparator$$$$schema$$$$schemaseparator$$$$table$$
We are looking for a permanent solution.
Best Regards,
Hans
Hans Bergsten
said
over 10 years ago
[This reply is migrated from our old forums.]
Re: Auto Completion ... is not always completing..
Hi Alex,
Okay, I'm able to reproduce it now. Thanks for reporting it.
Best Regards,
Hans
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed] [Attachment has been removed.]
Re: Auto Completion ... is not always completing..
Yes,
This is an existing table. See attached jpg.
Thanks.
Hans Bergsten
said
over 10 years ago
[This reply is migrated from our old forums.]
Re: Auto Completion ... is not always completing..
Hi Alex,
Do you mean that this happen even though tempdb.guest.GreenSheetsStaging is an existing table? I get the same trace if I try with a non-existing table (which is basically what the error message says) but not if I auto complete after WHERE for an existing table. Please clarify.
Best Regards,
Hans
a
anonymous
said
over 10 years ago
[This reply is migrated from our old forums. The original author name has been removed]
Re: Auto Completion ... is not always completing..
Hi
select *
from *tempdb*.*guest*.GreenSheetsStaging
where ..
Debug window:
09:06:20 [DEBUG ExecutorRunner-pool-2-thread-45 J.execute] Executing...
09:06:20 [DEBUG pool-3-thread-71 C.?] RootConnection: SybConnection.createStatement()
09:06:20 [DEBUG pool-3-thread-71 B.?] RootConnection: SybStatement.execute("SELECT * FROM guest.GreenSheetsStaging WHERE 1 = 0")
09:06:20 [DEBUG pool-3-thread-71 B.?] RootConnection: EXCEPTION -> com.sybase.jdbc4.jdbc.SybSQLException: guest.GreenSheetsStaging not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
com.sybase.jdbc4.jdbc.SybSQLException: guest.GreenSheetsStaging not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
at com.sybase.jdbc4.tds.Tds.processEed(Tds.java:4013)
at com.sybase.jdbc4.tds.Tds.nextResult(Tds.java:3103)
at com.sybase.jdbc4.jdbc.ResultGetter.nextResult(ResultGetter.java:79)
at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:290)
at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:272)
at com.sybase.jdbc4.jdbc.SybStatement.executeLoop(SybStatement.java:2594)
at com.sybase.jdbc4.jdbc.SybStatement.execute(SybStatement.java:2581)
at com.sybase.jdbc4.jdbc.SybStatement.execute(SybStatement.java:1293)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.onseven.dbvis.g.B.B.?(Z:104)
at com.onseven.dbvis.g.B.F$A.call(Z:1474)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
09:06:20 [DEBUG ExecutorRunner-pool-2-thread-45 A.?] AutoComplete exception
com.onseven.dbvis.J.B.O: com.sybase.jdbc4.jdbc.SybSQLException: guest.GreenSheetsStaging not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
at com.onseven.dbvis.J.B.J.execute(Z:2864)
at com.onseven.dbvis.J.B.Y.?(Z:1386)
at com.onseven.dbvis.J.B.Y.run(Z:337)
at com.onseven.dbvis.J.B.W.?(Z:2431)
at com.onseven.dbvis.J.B.W.?(Z:1021)
at com.onseven.dbvis.J.B.W.?(Z:284)
at com.onseven.dbvis.f.A.A$7.?(Z:763)
at com.onseven.dbvis.J.B.A.I.execute(Z:2291)
at com.onseven.dbvis.J.B.Y.?(Z:1386)
at com.onseven.dbvis.J.B.K.?(Z:1374)
at com.onseven.dbvis.J.B.K.doInBackground(Z:1521)
at javax.swing.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at javax.swing.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.sybase.jdbc4.jdbc.SybSQLException: guest.GreenSheetsStaging not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
at com.sybase.jdbc4.tds.Tds.processEed(Tds.java:4013)
at com.sybase.jdbc4.tds.Tds.nextResult(Tds.java:3103)
at com.sybase.jdbc4.jdbc.ResultGetter.nextResult(ResultGetter.java:79)
at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:290)
at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:272)
at com.sybase.jdbc4.jdbc.SybStatement.executeLoop(SybStatement.java:2594)
at com.sybase.jdbc4.jdbc.SybStatement.execute(SybStatement.java:2581)
at com.sybase.jdbc4.jdbc.SybStatement.execute(SybStatement.java:1293)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.onseven.dbvis.g.B.B.?(Z:104)
at com.onseven.dbvis.g.B.F$A.call(Z:1474)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
... 3 more
anonymous