Question about setting/saving parms in Visual SQL tool?

[JFCornwall]

Hi, first time posting here in the forum (though I did follow the old comp.database.ingres newsgroup for years).

My question is about the Visual SQL tool, version 9.1.0 running on Windows XP, connecting to various databases on Solaris boxes. Is there a way to make the program remember the settings for things like my user name and group? As installed, it always comes up with my first defined vnode shown in the picklist, then <Please Select a Database>, <Default Server>, <Default User> and <Default Group> for the parameters you have to specify to connect. (ignoring the Role since it doesn't apply to the way we operate).

What I would like is to have the program either retain these assorted values and reuse them the next time I start it up, or be able to specify them with a command line parameter of argument or something, so I can configure Windows to always use my userid and not be forced to scroll down a long list to get there every time I start it up.

So far, searches of this forum and the Help file for Visual SQl have not found anything.

Thanks in advance,

Jim Cornwall

[bilgihan]

Hello Jim,

unfortunately it seems there is no way to save the attributes.
Would it be an option for you, when you start Visual SQL from command line with appropriate parameters?
vdbasql .... options.
I've attached a screen shot from the options.

You could use a 'bat' file or whatever to use different options.
Bilgihan

[prodigygroupindia]

Jim,
There isn't any such known option so far but command line option should be a good way to do it if you wish to partially automate your tasks.

Thanks,
Venkat

[rhann]

Originally Posted by JFCornwall

Hi, first time posting here in the forum (though I did follow the old comp.database.ingres newsgroup for years).

Don't give up on comp.databases.ingres. The discussions there tend to go on longer and seem to cover more ground than they do here. I find I have to monitor both. Check out Comp.databases.ingres - Ingres Community Wiki which has links describing various different ways to access c.d.i.

One day we might persuade Ingres Corp to cross-post between the Ingres Forums and c.d.i. It would be the "open" thing to do.

[JFCornwall]

Originally Posted by bilgihan

Hello Jim,

unfortunately it seems there is no way to save the attributes.
Would it be an option for you, when you start Visual SQL from command line with appropriate parameters?
vdbasql .... options.
I've attached a screen shot from the options.

You could use a 'bat' file or whatever to use different options.
Bilgihan

Originally Posted by prodigygroupindia

Jim,
There isn't any such known option so far but command line option should be a good way to do it if you wish to partially automate your tasks.

Thanks,
Venkat

It did partly accomplish what I wanted, thanks. I'll explore that option further. I could get the settings (all but the <Default Group>) specified on a command line, but wasn't able to get them specified in a Windows shortcut. I'll play around some more...

command line used with greatest success was:

>vdbasql.exe -node=read -database=nwisne -ujcorn

As far as group setting I tried -gnwis_select, -Gnwis_select, -group=nwis_select... -group= gave me an error msg, -g and -G seemed to have no effect (still came up looking for <Default Group> in the program).

Maybe I have just missed it, but is the command line syntax documented somewhere accessible from the web?

Originally Posted by rhann

Don't give up on comp.databases.ingres. The discussions there tend to go on longer and seem to cover more ground than they do here. I find I have to monitor both. Check out Comp.databases.ingres - Ingres Community Wiki which has links describing various different ways to access c.d.i.

One day we might persuade Ingres Corp to cross-post between the Ingres Forums and c.d.i. It would be the "open" thing to do.

Maybe my ISP just dropped the group. I'll check that link and see if there's some way that doesn't involve (ack, spit, blargh...) Google Groups... (EDIT) - just checked my newgroups and the ISP's subscribe list, and the one I have with no recent activity was comp.database.ingres, while there are lots of posts in comp.databases.ingres... I certainly don't recall changing my subscriptions anytime in the last year or so, but perhaps I did. Mea Culpa :/

Thanks all

Jim

[bilgihan]

Hi Jim,

here from the manuals:
http://docs.ingres.com/Ingres/9.2/Co...ncmd.htm#o1452

vdbasql.exe -help shows available options. 'group' is not part of it

Bilgihan

[quida01]

Hi Jim,

Just to add a little more to this thread and digressing a tad more from the original question.

While there appears to be nothing in the doco as Biligihan has correctly pointed out about being able to specify a groupname on the command line call of vdbasql I did find that there was bug 120753 logged for this exact problem, the bug description follows:

“vdbasql has a -G option, but it doesn't work”

To cut a long story short there have been fixes coded for this problem and distributed via patches for 9.1.1, 9.1.2 and 9.2 that fix the problem i.e. specifying a groupname on the command line call to vdbasql (and –R<role> as well).

Doesn’t help you on 9.1.0 I know but it is fixed on later releases with a patch containing the fix for bug 120753.

Cheers, David

[JFCornwall]

Originally Posted by bilgihan

Hi Jim,

here from the manuals:
http://docs.ingres.com/Ingres/9.2/Co...ncmd.htm#o1452

vdbasql.exe -help shows available options. 'group' is not part of it

Bilgihan

Thanks for the link!

Originally Posted by quida01

Hi Jim,

Just to add a little more to this thread and digressing a tad more from the original question.

While there appears to be nothing in the doco as Biligihan has correctly pointed out about being able to specify a groupname on the command line call of vdbasql I did find that there was bug 120753 logged for this exact problem, the bug description follows:

“vdbasql has a -G option, but it doesn't work”

To cut a long story short there have been fixes coded for this problem and distributed via patches for 9.1.1, 9.1.2 and 9.2 that fix the problem i.e. specifying a groupname on the command line call to vdbasql (and –R<role> as well).

Doesn’t help you on 9.1.0 I know but it is fixed on later releases with a patch containing the fix for bug 120753.

Cheers, David

Thanks for looking at it. I'll see if I can pursuade my organization to update to 9.2...

Jim