squirrel-sql-users — A subscriber only discussion list for SQuirreL

Re: [Squirrel-sql-users] Catalog drop-down box

[Gerd W. <ger...@t-...>]

On 10/24/25 22:25, info wrote:
> Hello, devs:
> 
> When refreshing tree and cache, from the object tree, the Catalog drop 
> down box above does not refresh. If a schema/database is added, the 
> whole alias tab has to be closed and reopened, to affect the creation. 
> Could you please add a few lines of code, to refresh Catalog as well, 
> please?
> 
> Many thanks!
> 
The following was implemented and will be available in future snapshots 
and versions.
Excerpt from change log:

For databases which support catalogs the "Refresh tree and Cache" function
   now refreshes the catalogs combo box, too.
   Info: To execute the refresh function use F5, toolbar or the Session 
menu --> "Refresh tree and Cache"

[Squirrel-sql-users] Catalog drop-down box

[info <in...@dr...>]

Hello, devs:

When refreshing tree and cache, from the object tree, the Catalog drop 
down box above does not refresh. If a schema/database is added, the 
whole alias tab has to be closed and reopened, to affect the creation. 
Could you please add a few lines of code, to refresh Catalog as well, 
please?

Many thanks!

Re: [Squirrel-sql-users] SQL tab

[Gerd W. <ger...@t-...>]

On 10/23/25 00:49, info wrote:
> Hello, devs:
> 
> Over the past few weeks I had to do a lot of work in Squirrel, and it 
> was a huge pain to switch between the SQL and Object tabs.
> When the SQL tab is active, the object tree is not visible, and vice 
> versa. Grr!
> The user experience would have been much more pleasant, were the SQL tab 
> not situated above the object tree, next to Objects, but right before 
> Info, to the right of the object tree. Then, there would have been no 
> need for the tab control that currently hosts the Objects and SQL tabs, 
> and the object tree would have been always visible, during the SQL 
> development, which would have allowed much more expedient interaction 
> with it.
> 
> Many thanks,
> 

You may try the Session tool bar button or the Session menu item "Show 
Object tree besides editor".

Gerd

[Squirrel-sql-users] SQL tab

[info <in...@dr...>]

Hello, devs:

Over the past few weeks I had to do a lot of work in Squirrel, and it 
was a huge pain to switch between the SQL and Object tabs.
When the SQL tab is active, the object tree is not visible, and vice 
versa. Grr!
The user experience would have been much more pleasant, were the SQL tab 
not situated above the object tree, next to Objects, but right before 
Info, to the right of the object tree. Then, there would have been no 
need for the tab control that currently hosts the Objects and SQL tabs, 
and the object tree would have been always visible, during the SQL 
development, which would have allowed much more expedient interaction 
with it.

Many thanks,

Re: [Squirrel-sql-users] [External Sender] Re: Viewing Check Constraints

[Gerd W. <ger...@t-...>]

On 10/17/25 22:06, David Clark wrote:
> Gerd,
> 
> I downloaded the 5.0.0 snapshot and installed it.  At installation time, 
> I also selected the optional DB2 plugin for installation.  However, when 
> I opened the client I did not find this new tab you mentioned.  So, how 
> do I get to this new constraints tab?
> 
> image.png
> 
> 
> image.png
> 
> 
> Thanks,
> Dave Clark
> 
Sorry, I can't reproduce your problem. The name "5.0.0 snapshot" sounds 
unusual. You can find the version with the change here

https://sourceforge.net/projects/squirrel-sql/files/3-snapshots/snapshot-20251013_2156/

or here

https://github.com/squirrel-sql-client/squirrel-sql-snapshot-releases/releases/tag/snapshot-20251013_2156

Gerd

Re: [Squirrel-sql-users] [External Sender] Re: Viewing Check Constraints

[Gerd W. <ger...@t-...>]

The following was implemented and will be available in future snapshots 
and versions:

 > DB2 Plugin: The table details in the Object tree has a new tab
 >   which displays Check Constraints for DB2 LUW.


Thanks for the SQL, Dave.

If someone knew the OS400 or ZOS version for Dave's Check Constraint SQL 
I'd be happy to include them in SQuirreL, too.

Gerd


On 6/23/25 14:39, David Clark wrote:
> Well, I've found that I can run a custom query for it.  Seems this could 
> be built in.  But, I do understand that the system table names may 
> change depending upon the connected DBMS.
> 
> Select trim(con.tabschema) || '.' || trim(con.tabname) as table
>       , con.constname as constraint_name
>       , case tab.enforced
>           when 'N' then 'Disabled'
>           when 'Y' then 'Active'
>         end as status
>       , col.colname as column_name
>       , cast(con.text as varchar(255)) as text
>    from syscat.checks as con
>    Join syscat.colchecks as col
>      on col.constname = con.constname
>     and col.tabschema = con.tabschema
>     and col.tabname = con.tabname
>    Join syscat.tabconst as tab
>      on tab.constname = con.constname
>     and tab.tabschema = con.tabschema
>     and tab.tabname = con.tabname
>   order by con.tabschema, con.tabname, col.colname;
> 
> Thanks,
> 
> Dave Clark
> -- 
> Winsupply Group Services
> 3110 Kettering Boulevard
> Dayton, Ohio  45439  USA
> (937) 294-5331
> 
> 
> On Sun, Jun 22, 2025 at 4:37 PM Gerd Wagner <ger...@t-... 
> <mailto:ger...@t-...>> wrote:
> 
> 
> 
>     On 11.06.25 16:26, David Clark wrote:
>      > I have found where to view indexes and foreign key constraints,
>     but not
>      > where to view check constraints.  Is this available in SQuirrel 4.8?
>      >
> 
>     No it's not.
> 
>     To my knowledge the JDBC-API does not offer access to check constraints
>     and there isn't any other SQL standard way to access check constraints,
>     either.
> 
>     Gerd
> 

Re: [Squirrel-sql-users] Accessing Same Database Name in Different Environments

[David C. <dl...@wi...>]

Note that I found how to catalog a database alias, but I don't understand
why I am getting this error.

db2 catalog database txvision as txvision_dev at node devnode
> SQL0104N  An unexpected token "txvision_dev" was found following "AS".
Expected tokens may include:  "<database-alias>".  SQLSTATE=42601

Sincerely,

Dave Clark
--
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


On Mon, Oct 6, 2025 at 9:11 AM David Clark <dl...@wi...> wrote:

> We have a DB2/LUW database in a full development life-cycle environment.
> As such, the same database name exists on different servers.  SQUirrell,
> itself, supports the use of aliases to handle this situation.  However, how
> do I do the same thing from the DB2 perspective?  Meaning, I already have
> the following for the development environment.
>
> db2 catalog tcpip node devnode remote larsond01 server 50000
> db2 catalog database txvision at node devnode
>
> But when I attempt to do the same for the QA environment, I get an error
> message.
>
> db2 catalog tcpip node qanode remote larsonq01 server 50000
> > DB20000I  The CATALOG TCPIP NODE command completed successfully.
> db2 catalog database txvision at node qanode
> > SQL1005N  The database alias "txvision" already exists in either the
> local
> database directory or system database directory.
>
> I can specify a unique TCPIP node name for the new server name, but not
> the same database name at the new node.  Is there a DB2 alias I can specify
> in this situation?
>
> Sincerely,
>
> Dave Clark
> --
> Winsupply Group Services
> 3110 Kettering Boulevard
> Dayton, Ohio  45439  USA
> (937) 294-5331
>

Re: [Squirrel-sql-users] Accessing Same Database Name in Different Environments

[David C. <dl...@wi...>]

OK, it looks like the answer is that database alias names cannot be more
than 8 characters in length.

Thanks,

Dave Clark
--
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


On Mon, Oct 6, 2025 at 10:13 AM David Clark <dl...@wi...> wrote:

> Note that I found how to catalog a database alias, but I don't understand
> why I am getting this error.
>
> db2 catalog database txvision as txvision_dev at node devnode
> > SQL0104N  An unexpected token "txvision_dev" was found following "AS".
> Expected tokens may include:  "<database-alias>".  SQLSTATE=42601
>
> Sincerely,
>
> Dave Clark
> --
> Winsupply Group Services
> 3110 Kettering Boulevard
> Dayton, Ohio  45439  USA
> (937) 294-5331
>
>
> On Mon, Oct 6, 2025 at 9:11 AM David Clark <dl...@wi...> wrote:
>
>> We have a DB2/LUW database in a full development life-cycle environment.
>> As such, the same database name exists on different servers.  SQUirrell,
>> itself, supports the use of aliases to handle this situation.  However, how
>> do I do the same thing from the DB2 perspective?  Meaning, I already have
>> the following for the development environment.
>>
>> db2 catalog tcpip node devnode remote larsond01 server 50000
>> db2 catalog database txvision at node devnode
>>
>> But when I attempt to do the same for the QA environment, I get an error
>> message.
>>
>> db2 catalog tcpip node qanode remote larsonq01 server 50000
>> > DB20000I  The CATALOG TCPIP NODE command completed successfully.
>> db2 catalog database txvision at node qanode
>> > SQL1005N  The database alias "txvision" already exists in either the
>> local
>> database directory or system database directory.
>>
>> I can specify a unique TCPIP node name for the new server name, but not
>> the same database name at the new node.  Is there a DB2 alias I can specify
>> in this situation?
>>
>> Sincerely,
>>
>> Dave Clark
>> --
>> Winsupply Group Services
>> 3110 Kettering Boulevard
>> Dayton, Ohio  45439  USA
>> (937) 294-5331
>>
>

[Squirrel-sql-users] Accessing Same Database Name in Different Environments

[David C. <dl...@wi...>]

We have a DB2/LUW database in a full development life-cycle environment.
As such, the same database name exists on different servers.  SQUirrell,
itself, supports the use of aliases to handle this situation.  However, how
do I do the same thing from the DB2 perspective?  Meaning, I already have
the following for the development environment.

db2 catalog tcpip node devnode remote larsond01 server 50000
db2 catalog database txvision at node devnode

But when I attempt to do the same for the QA environment, I get an error
message.

db2 catalog tcpip node qanode remote larsonq01 server 50000
> DB20000I  The CATALOG TCPIP NODE command completed successfully.
db2 catalog database txvision at node qanode
> SQL1005N  The database alias "txvision" already exists in either the local
database directory or system database directory.

I can specify a unique TCPIP node name for the new server name, but not the
same database name at the new node.  Is there a DB2 alias I can specify in
this situation?

Sincerely,

Dave Clark
--
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331

Re: [Squirrel-sql-users] MySQL bit(n) fields are displayed as true/false

[Gerd W. <ger...@t-...>]

On 9/14/25 18:15, John Hardin wrote:
> On Sat, 13 Sep 2025, Gerd Wagner wrote:
>> On 9/11/25 19:51, info wrote:
>>>  SquirrelSQL 4.8.0 displays bit(n) fields where n>1 as true/false, 
>>> whereas
>>>  they should be displayed as integers of the corresponding width as for
>>>  example MySQL Workbench does.
>>>
>>
>> Sorry, I can't reproduce you problem.
>> My MYSQL DB does not allow values other than 0, 1, true, false in 
>> columns of type BIT. I'm using MySQL version 8.0.17 and JDBC-Driver 
>> "MySQL Connector/J" version mysql-connector-java-8.0.15
>>
>> Gerd
> 
> That sounds incorrect (or at least _incomplete_) per the documentation:
> 
>    https://docs.oracle.com/cd/E17952_01/mysql-8.4-en/bit-type.html
> 
> "bit(n)" is not a single bit, it's an array of n bits.
> 
> Squirrel should be aware of "bit" vs. "bit(n)" and should not display 
> data in a column of type "bit(n>1)" as just true/false. That is (badly) 
> mininterpreting the data.
> 
> I'd suggest the best default is the native "b'value'" notation from the 
> documentation, but that might not be easily platform-portable. Does 
> Squirrel support other platform-specific display formatting for 
> platform-specific data types?
> 
>    https://docs.oracle.com/cd/E17952_01/mysql-8.4-en/bit-value- 
> literals.html
> 
> The alternative would be to display them as integers as the OP says 
> MySQL Workbench does.
> 
> "In numeric contexts, MySQL treats a bit literal like an integer. To 
> ensure numeric treatment of a bit literal, use it in numeric context. 
> Ways to do this include adding 0 or using CAST(... AS UNSIGNED)."
> 
> OP: For the moment you can probably work around this by querying 
> "CAST(bitn_col AS UNSIGNED)", "(bitn_col + 0)" or "BIN(bitn_col)" as 
> noted in the MySQL bit-value-literals documentation, rather than 
> querying just raw "bitn_col".
> 
> OP: I suggest opening a bug for this in the bug tracker referenced from 
> the Squirrel home page:
> 
>    https://github.com/squirrel-sql-client/squirrel-sql-code/issues
> 

Ups, sorry, I didn't pay intention to the (n) of bit(n).

I checked it out now. The problem is that bit(n) is not a common SQL 
data type, at least there seems no appropriate representation in the JDK 
class java.sql.Types. This might be the reason why the implementers of 
the MySQL JDBC driver decided to deliver the type BIT(=-7) for columns 
of type bit(n). A probably better choice would have been INTEGER(=4).

I attach a short Java program that reproduces the problem. You may want 
to contact the JDCB driver implementers about this issue.

Gerd

P.S.: Your workaround CAST(bitArrayTestValue AS UNSIGNED) works for me, too.

Re: [Squirrel-sql-users] MySQL bit(n) fields are displayed as true/false

[John H. <jh...@im...>]

On Sat, 13 Sep 2025, Gerd Wagner wrote:
> On 9/11/25 19:51, info wrote:
>>  SquirrelSQL 4.8.0 displays bit(n) fields where n>1 as true/false, whereas
>>  they should be displayed as integers of the corresponding width as for
>>  example MySQL Workbench does.
>> 
>
> Sorry, I can't reproduce you problem.
> My MYSQL DB does not allow values other than 0, 1, true, false in columns of 
> type BIT. I'm using MySQL version 8.0.17 and JDBC-Driver "MySQL Connector/J" 
> version mysql-connector-java-8.0.15
>
> Gerd

That sounds incorrect (or at least _incomplete_) per the documentation:

   https://docs.oracle.com/cd/E17952_01/mysql-8.4-en/bit-type.html

"bit(n)" is not a single bit, it's an array of n bits.

Squirrel should be aware of "bit" vs. "bit(n)" and should not display data 
in a column of type "bit(n>1)" as just true/false. That is (badly) 
mininterpreting the data.

I'd suggest the best default is the native "b'value'" notation from the 
documentation, but that might not be easily platform-portable. Does 
Squirrel support other platform-specific display formatting for 
platform-specific data types?

   https://docs.oracle.com/cd/E17952_01/mysql-8.4-en/bit-value-literals.html

The alternative would be to display them as integers as the OP says MySQL 
Workbench does.

"In numeric contexts, MySQL treats a bit literal like an integer. To 
ensure numeric treatment of a bit literal, use it in numeric context. Ways 
to do this include adding 0 or using CAST(... AS UNSIGNED)."

OP: For the moment you can probably work around this by querying 
"CAST(bitn_col AS UNSIGNED)", "(bitn_col + 0)" or "BIN(bitn_col)" as noted 
in the MySQL bit-value-literals documentation, rather than querying just 
raw "bitn_col".

OP: I suggest opening a bug for this in the bug tracker referenced from 
the Squirrel home page:

   https://github.com/squirrel-sql-client/squirrel-sql-code/issues


-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jh...@im...                         pgpk -a jh...@im...
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   Gun Control laws aren't enacted to control guns, they are enacted
   to control people: catholics (1500s), japanese peasants (1600s),
   blacks (1860s), italian immigrants (1911), armenians (1911),
   the irish (1920s), jews (1930s), blacks (1960s), the poor (always)
-----------------------------------------------------------------------
  3 days until the 238th anniversary of the signing of the U.S. Constitution

Re: [Squirrel-sql-users] MySQL bit(n) fields are displayed as true/false

[Gerd W. <ger...@t-...>]

On 9/11/25 19:51, info wrote:
> SquirrelSQL 4.8.0 displays bit(n) fields where n>1 as true/false, 
> whereas they should be displayed as integers of the corresponding width 
> as for example MySQL Workbench does.
> 

Sorry, I can't reproduce you problem.
My MYSQL DB does not allow values other than 0, 1, true, false in 
columns of type BIT. I'm using MySQL version 8.0.17 and JDBC-Driver 
"MySQL Connector/J" version mysql-connector-java-8.0.15

Gerd

Re: [Squirrel-sql-users] Save preferences

[Gerd W. <ger...@t-...>]

Another option can be found at menu File --> Global Preferences --> tab 
General --> radio button at the right named "Save Aliases and Drivers 
immediately"

Gerd

On 9/11/25 01:59, Roger Hill wrote:
> File/Save preferences
> 
> Roger
> 
> 
> _______________________________________________
> Squirrel-sql-users mailing list
> Squ...@li...
> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users

[Squirrel-sql-users] MySQL bit(n) fields are displayed as true/false

[info <in...@dr...>]

SquirrelSQL 4.8.0 displays bit(n) fields where n>1 as true/false, 
whereas they should be displayed as integers of the corresponding width 
as for example MySQL Workbench does.

[Squirrel-sql-users] Save preferences

[Roger H. <rh...@hi...>]

File/Save preferences 
 
 
 
 
 Roger

Re: [Squirrel-sql-users] Changes to aliases are lost if the OS crashes after edits but before exiting the application

[info <in...@dr...>]

Does anyone know who is the developer who decided that it is a good idea 
to introduce a separate menu item for the saving of the settings?

On 2025-09-10 07:53 PM, Roger Hill wrote:
> There is a 'save preferences' button that is clickable. I am not near 
> my computer at the moment, but it is there in the menu structure.
>
> Roger
>
> Get BlueMail for Mobile <https://bluemail.me/download/>
> On 10 September 2025, at 7:38 pm, info <in...@dr... 
> <mailto:in...@dr...>> wrote:
>
>
>> What are you referring to as 'Save preferences'?
>>
>> On 2025-09-10 07:35 PM, Roger Hill wrote:
>>> You never said that you clicked on 'Save preferences'.
>>>
>>> That has worked for me for many years.
>>>
>>> Regards
>>> Roger
>>>
>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>> On 10 September 2025, at 7:32 pm, info <in...@dr... 
>>> <mailto:in...@dr...>> wrote:
>>>
>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>
>> What are you referring to as 'Save preferences'?
>>
>> On 2025-09-10 07:35 PM, Roger Hill wrote:
>>> You never said that you clicked on 'Save preferences'.
>>>
>>> That has worked for me for many years.
>>>
>>> Regards
>>> Roger
>>>
>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>> On 10 September 2025, at 7:32 pm, info <in...@dr... 
>>> <mailto:in...@dr...>> wrote:
>>>
>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>
>> What are you referring to as 'Save preferences'?
>>
>> On 2025-09-10 07:35 PM, Roger Hill wrote:
>>> You never said that you clicked on 'Save preferences'.
>>>
>>> That has worked for me for many years.
>>>
>>> Regards
>>> Roger
>>>
>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>> On 10 September 2025, at 7:32 pm, info <in...@dr... 
>>> <mailto:in...@dr...>> wrote:
>>>
>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>>> I described the contrary in enough detail.
>>>>
>>>>
>>>>
>>>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>>>> If you save preferences after the changes, they will be retained.
>>>>>
>>>>> Roger
>>>>>
>>>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>>>> <mailto:in...@dr...>> wrote:
>>>>>
>>>>>
>>>>>> I edited aliases: cloned one, edited values, saved, and renamed 
>>>>>> the old one. Then I did some work within the new alias: created 
>>>>>> tables, ran queries.
>>>>>> A few hours later, while the same instance Squirrel 4.8.0 was 
>>>>>> still running, the OS hung, and the kernel panicked.
>>>>>> After the reboot, there was no new alias in the list, and the old 
>>>>>> one had the earlier name, so none of the changed have been committed.
>>>>>> In the ideal world, they should be committed immediately, not 
>>>>>> when the application exits, which seems to be the case.
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Squirrel-sql-users mailing list
>>>>>> Squ...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>>>
>>>>
>>

Re: [Squirrel-sql-users] Changes to aliases are lost if the OS crashes after edits but before exiting the application

[info <in...@dr...>]

What are you referring to as 'Save preferences'?

On 2025-09-10 07:35 PM, Roger Hill wrote:
> You never said that you clicked on 'Save preferences'.
>
> That has worked for me for many years.
>
> Regards
> Roger
>
> Get BlueMail for Mobile <https://bluemail.me/download/>
> On 10 September 2025, at 7:32 pm, info <in...@dr... 
> <mailto:in...@dr...>> wrote:
>
>
>> I described the contrary in enough detail.
>>
>>
>>
>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>> If you save preferences after the changes, they will be retained.
>>>
>>> Roger
>>>
>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>> <mailto:in...@dr...>> wrote:
>>>
>>>
>>>> I edited aliases: cloned one, edited values, saved, and renamed the 
>>>> old one. Then I did some work within the new alias: created tables, 
>>>> ran queries.
>>>> A few hours later, while the same instance Squirrel 4.8.0 was still 
>>>> running, the OS hung, and the kernel panicked.
>>>> After the reboot, there was no new alias in the list, and the old 
>>>> one had the earlier name, so none of the changed have been committed.
>>>> In the ideal world, they should be committed immediately, not when 
>>>> the application exits, which seems to be the case.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Squirrel-sql-users mailing list
>>>> Squ...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>
>>
>> I described the contrary in enough detail.
>>
>>
>>
>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>> If you save preferences after the changes, they will be retained.
>>>
>>> Roger
>>>
>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>> <mailto:in...@dr...>> wrote:
>>>
>>>
>>>> I edited aliases: cloned one, edited values, saved, and renamed the 
>>>> old one. Then I did some work within the new alias: created tables, 
>>>> ran queries.
>>>> A few hours later, while the same instance Squirrel 4.8.0 was still 
>>>> running, the OS hung, and the kernel panicked.
>>>> After the reboot, there was no new alias in the list, and the old 
>>>> one had the earlier name, so none of the changed have been committed.
>>>> In the ideal world, they should be committed immediately, not when 
>>>> the application exits, which seems to be the case.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Squirrel-sql-users mailing list
>>>> Squ...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>
>>
>> I described the contrary in enough detail.
>>
>>
>>
>> On 2025-09-10 06:04 PM, Roger Hill wrote:
>>> If you save preferences after the changes, they will be retained.
>>>
>>> Roger
>>>
>>> Get BlueMail for Mobile <https://bluemail.me/download/>
>>> On 10 September 2025, at 6:03 pm, info <in...@dr... 
>>> <mailto:in...@dr...>> wrote:
>>>
>>>
>>>> I edited aliases: cloned one, edited values, saved, and renamed the 
>>>> old one. Then I did some work within the new alias: created tables, 
>>>> ran queries.
>>>> A few hours later, while the same instance Squirrel 4.8.0 was still 
>>>> running, the OS hung, and the kernel panicked.
>>>> After the reboot, there was no new alias in the list, and the old 
>>>> one had the earlier name, so none of the changed have been committed.
>>>> In the ideal world, they should be committed immediately, not when 
>>>> the application exits, which seems to be the case.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Squirrel-sql-users mailing list
>>>> Squ...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
>>
>>

Re: [Squirrel-sql-users] Changes to aliases are lost if the OS crashes after edits but before exiting the application

[Roger H. <rh...@hi...>]

You never said that you clicked on 'Save preferences'. 
 
 
 
 
 That has worked for me for many years. 
 
 
 
 
 Regards 
 
 Roger  
 
 
 
 
 
 
 
 
     
  
  
     
     
       
 
         
         
 
           
 If you save preferences after the changes,
            they will be retained. 
 
           
 
 
           
 
           
 Roger 
 
           
 
 
           
 
           
         
 
         
         
 
         
 
         
 
           
             
 I edited aliases: cloned one, edited values, saved, and
              renamed the old one. Then I did some work within the new
              alias: created tables, ran queries. 
 
             
 A few hours later, while the same instance Squirrel
              4.8.0 was still running, the OS hung, and the kernel
              panicked. 
 
             
 After the reboot, there was no new alias in the list,
              and the old one had the earlier name, so none of the
              changed have been committed. 
 
             
 In the ideal world, they should be committed
              immediately, not when the application exits, which seems
              to be the case. 
 
             
 
 
             
 
             
 
 
             
 
             
 
 
             
 
             
 _______________________________________________ 
 
             
 Squirrel-sql-users mailing list 
 
             
 Squ...@li... 
 
             
 https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users 
 
           
         
 
       
 
     
     
 
     
  
 
 
 
     
  
  
     
     
       
 
         
         
 
           
 If you save preferences after the changes,
            they will be retained. 
 
           
 
 
           
 
           
 Roger 
 
           
 
 
           
 
           
         
 
         
         
 
         
 
         
 
           
             
 I edited aliases: cloned one, edited values, saved, and
              renamed the old one. Then I did some work within the new
              alias: created tables, ran queries. 
 
             
 A few hours later, while the same instance Squirrel
              4.8.0 was still running, the OS hung, and the kernel
              panicked. 
 
             
 After the reboot, there was no new alias in the list,
              and the old one had the earlier name, so none of the
              changed have been committed. 
 
             
 In the ideal world, they should be committed
              immediately, not when the application exits, which seems
              to be the case. 
 
             
 
 
             
 
             
 
 
             
 
             
 
 
             
 
             
 _______________________________________________ 
 
             
 Squirrel-sql-users mailing list 
 
             
 Squ...@li... 
 
             
 https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users 
 
           
         
 
       
 
     
     
 
     
  
 
 
 
     
  
  
     
     
       
 
         
         
 
           
 If you save preferences after the changes,
            they will be retained. 
 
           
 
 
           
 
           
 Roger 
 
           
 
 
           
 
           
         
 
         
         
 
         
 
         
 
           
             
 I edited aliases: cloned one, edited values, saved, and
              renamed the old one. Then I did some work within the new
              alias: created tables, ran queries. 
 
             
 A few hours later, while the same instance Squirrel
              4.8.0 was still running, the OS hung, and the kernel
              panicked. 
 
             
 After the reboot, there was no new alias in the list,
              and the old one had the earlier name, so none of the
              changed have been committed. 
 
             
 In the ideal world, they should be committed
              immediately, not when the application exits, which seems
              to be the case. 
 
             
 
 
             
 
             
 
 
             
 
             
 
 
             
 
             
 _______________________________________________ 
 
             
 Squirrel-sql-users mailing list 
 
             
 Squ...@li... 
 
             
 https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users

Re: [Squirrel-sql-users] Changes to aliases are lost if the OS crashes after edits but before exiting the application

[info <in...@dr...>]

I described the contrary in enough detail.



On 2025-09-10 06:04 PM, Roger Hill wrote:
> If you save preferences after the changes, they will be retained.
>
> Roger
>
> Get BlueMail for Mobile <https://bluemail.me/download/>
> On 10 September 2025, at 6:03 pm, info <in...@dr... 
> <mailto:in...@dr...>> wrote:
>
>
>> I edited aliases: cloned one, edited values, saved, and renamed the 
>> old one. Then I did some work within the new alias: created tables, 
>> ran queries.
>> A few hours later, while the same instance Squirrel 4.8.0 was still 
>> running, the OS hung, and the kernel panicked.
>> After the reboot, there was no new alias in the list, and the old one 
>> had the earlier name, so none of the changed have been committed.
>> In the ideal world, they should be committed immediately, not when 
>> the application exits, which seems to be the case.
>>
>>
>>
>> _______________________________________________
>> Squirrel-sql-users mailing list
>> Squ...@li...
>> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users

Re: [Squirrel-sql-users] Changes to aliases are lost if the OS crashes after edits but before exiting the application

[Roger H. <rh...@hi...>]

If you save preferences after the changes, they will be retained. 
  
  
  
  
  Roger 
  
  
  
  
  
  
  
  
  I edited aliases: cloned one, edited values, saved, and renamed the old 
one. Then I did some work within the new alias: created tables, ran 
queries. 
  
  A few hours later, while the same instance Squirrel 4.8.0 was still 
running, the OS hung, and the kernel panicked. 
  
  After the reboot, there was no new alias in the list, and the old one had 
the earlier name, so none of the changed have been committed. 
  
  In the ideal world, they should be committed immediately, not when the 
application exits, which seems to be the case. 
  
  
  
  
  
  
  
  
  
  
  _______________________________________________ 
  
  Squirrel-sql-users mailing list 
  
  Squ...@li... 
  
  https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users

[Squirrel-sql-users] Changes to aliases are lost if the OS crashes after edits but before exiting the application

[info <in...@dr...>]

I edited aliases: cloned one, edited values, saved, and renamed the old 
one. Then I did some work within the new alias: created tables, ran queries.
A few hours later, while the same instance Squirrel 4.8.0 was still 
running, the OS hung, and the kernel panicked.
After the reboot, there was no new alias in the list, and the old one 
had the earlier name, so none of the changed have been committed.
In the ideal world, they should be committed immediately, not when the 
application exits, which seems to be the case.

Re: [Squirrel-sql-users] [External Sender] Re: Viewing Check Constraints

[David C. <dl...@wi...>]

Well, I've found that I can run a custom query for it.  Seems this could be
built in.  But, I do understand that the system table names may change
depending upon the connected DBMS.

Select trim(con.tabschema) || '.' || trim(con.tabname) as table
     , con.constname as constraint_name
     , case tab.enforced
         when 'N' then 'Disabled'
         when 'Y' then 'Active'
       end as status
     , col.colname as column_name
     , cast(con.text as varchar(255)) as text
  from syscat.checks as con
  Join syscat.colchecks as col
    on col.constname = con.constname
   and col.tabschema = con.tabschema
   and col.tabname = con.tabname
  Join syscat.tabconst as tab
    on tab.constname = con.constname
   and tab.tabschema = con.tabschema
   and tab.tabname = con.tabname
 order by con.tabschema, con.tabname, col.colname;

Thanks,

Dave Clark
--
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


On Sun, Jun 22, 2025 at 4:37 PM Gerd Wagner <ger...@t-...> wrote:

>
>
> On 11.06.25 16:26, David Clark wrote:
> > I have found where to view indexes and foreign key constraints, but not
> > where to view check constraints.  Is this available in SQuirrel 4.8?
> >
>
> No it's not.
>
> To my knowledge the JDBC-API does not offer access to check constraints
> and there isn't any other SQL standard way to access check constraints,
> either.
>
> Gerd
>

Re: [Squirrel-sql-users] Viewing Check Constraints

[Gerd W. <ger...@t-...>]

On 11.06.25 16:26, David Clark wrote:
> I have found where to view indexes and foreign key constraints, but not 
> where to view check constraints.  Is this available in SQuirrel 4.8?
> 

No it's not.

To my knowledge the JDBC-API does not offer access to check constraints 
and there isn't any other SQL standard way to access check constraints, 
either.

Gerd

Re: [Squirrel-sql-users] Unsubscribe

[Stanimir S. <s7...@ne...>]

Wed, 11 Jun 2025 14:58:26 +0000, /Kevin Beard/:

> To: "squ...@li..."
>  <squ...@li...>
> List-Unsubscribe: <https://lists.sourceforge.net/lists/options/squirrel-sql-users>, 
>  <mailto:squ...@li...?subject=unsubscribe>
> 
> Unsubscribe

I guess you need to send this to 
<squ...@li...>, instead.

-- 
Stanimir

[Squirrel-sql-users] Unsubscribe

[Kevin B. <Kev...@ph...>]

Unsubscribe

This message and any attachments are confidential, may contain privileged information, and are intended solely for the recipient named above.
If you are not the intended recipient, or a person responsible for delivery to the named recipient, you are notified that any review, distribution, dissemination or copying is prohibited.
If you have received this message in error, you should notify the sender by return email and delete the message from your computer system.