Recent changes to feature-requests

#135 connection initialization

2018-11-20T18:41:17.877000Z

Is there a way to incorporate Miktex and several software packages for Mathematical-Physics Typesettings, such as AMS, Physics, HEP, etc. For those engaged in collaborative projects that require Latex 2e or the newest Latex 3 project packages, this would be of tremendous help. Issues are uploading all Latex packages and Editors (such as Tex Studio), assimilating them into one unified editor.

connection initialization

2013-08-08T10:18:16.133000Z

Provide the possibility to specify a list of statements to execute upon connect, like in the commons-dbcp parameter "connectionInitSqls" resource configuration.
On the bookmark "Options" tag a textarea could be added to contain initialization statements, one per line and separated by semi-columns.
Connection initialization statements could be used, for example, to alter session configuration automatically.
For a Oracle connection one could write, for example:
ALTER SESSION SET NLS_COMP=LINGUISTIC;
ALTER SESSION SET NLS_SORT=BINARY_CI;
and obtain a case insensitive search and ordering that can't be achieved using dialogs without having to issue the commands on every connection opening.
Thanks

sybase and lower/upper case

2010-03-29T12:15:22Z

hi,

I use quantum 3.3.0 from longtime with sybase.
I try to use the latest version 3.3.9 and I think there is a problem.
When I click on an table, in order to see the datas , I have this error : "DBO"."MY_TABLE" not found....."

In fact the problem is that the query use uppercase,

If I try a query "select * from dbo.my_table....." it' runs
but if I try the query "select * from DBO.MY_TABLE...", the same error appears.

So why the plugin use uppercase and not lowercase ?
Is there a option to force to use lower case ?

Regards

sybase and lower/upper case

2010-03-29T12:04:06Z

hi,

In fact the problem is that the query use uppercase,

If I try a query "select * from dbo.my_table....." it' runs
but if I try the query "select * from DBO.MY_TABLE...", the same error appears.

So why the plugin use uppercase and not lowercase ?
Is there a option to force to use lower case ?

Regards

sybase and lower/upper case

2010-03-29T11:00:14Z

hi,

In fact the problem is that the query use uppercase,

If I try a query "select * from dbo.my_table....." it' runs
but if I try the query "select * from DBO.MY_TABLE...", the same error appears.

So why the plugin use uppercase and not lowercase ?
Is there a option to force to use lower case ?

Regards

Add support for H2 Database

2009-07-14T20:50:46Z

If you haven't heard of it: http://www.h2database.com/
If I see that correct I only need to implement a class which extends DatabaseAdapter and add this class to the AdapterFactory. Then I'll probably write a patch soon...

Display nicknames for DB2

2008-10-15T20:33:06Z

Currently DB2 only shows Sequences, tables, views, and aliases. Please add nicknames.

Commit/Rollback

2008-07-31T10:14:02Z

I have found that when performing updates while viewing tables, there is no interface-driven facility (that I can see) for explicitly committing or rolling-back the data change. Using the box that appears after selecting "Update" from the right-click menu when viewing a table obviously requires that the "Where" boxes be checked for the fields that uniquely identify the record(s) to be edited, and if this is forgotten the change seems to be instantaneously committed upon clicking "Finish" - this can be dangerous, and it would be very helpful if there were buttons and/or menus for commit/rollback.

Improve Large OBject fields in QuantumDB

2008-07-31T10:07:27Z

When viewing tables via Oracle 10g clients (thin or regular), only up to 4kb of data appears or can be edited. It seems likely this is because of how ?LOBs are stored - <=4kb in the table and >4kb separately.

Can Quantum DB be changed to accommodate the whole Large OBject field contents for viewing/editing please?

enable per database override of uses/usedby

2008-04-12T20:08:27Z

On large databases the usedby logic, whilst working fine, is not necessarily the fastest solution. In Sybase at least, a system stored procedure would provide the list of dependent objects much faster than the default code can. Could the database adaptor override the default method?