Reverse merged rev. 6812 which is everything under .../tags/2.7.3/trunk
Release tag 2.7.4
Release tag 2.7.4
Release tag 2.7.3
Release prep
Removing tag created incorrectly
Make default global logging level more restrictive for performance reasons per suggestion by siggemannen. No matches JDK global default.
That file isn't loaded unless Java sys property hsqldb.reconfig_logging is set to true.
Fix is in. The next HyperSQL release with have it. Until then you can build a sqltool jar yourself with current trunk. On Fri, Nov 18, 2022 at 2:07 AM Dushyant Shinde dushyant-ds@users.sourceforge.net wrote: Thanks for the reply. Actually, the SQL tool and hsqldb both dependencies were detected for a security issue under this CVE-2022-41853 id. We are therefore unable to use the previous version (2.4.1) of the sqltool. So is there any other workaround? Issues upgrading to hsqldb and sqltool version...
Issues upgrading to hsqldb and sqltool version from 2.4.1 to 2.7.1
Fix applied with revision 6632.
Fix for bug #1667. Added missing index incrementer that broke multiple-input-file invocations.
Issues upgrading to hsqldb and sqltool version from 2.4.1 to 2.7.1
Root cause found. With commit 5862 when enhancing to support URLs generally (as opposed to local file paths), I somehow lost the ++ postfix operator in increment an index, and there happens to be no unit test to cover multiple SQL files in a single invocation. Fix is to just insert the two + characters and I'll do that now.
Great idea, Fred. I verified that this works: java -cp /local/hsqldb-2.4.1/lib/sqltool.jar:/local/hsqldb/lib/hsqldb.jar org.hsqldb.cmdline.SqlTool --inlineRc=URL=jdbc:hsqldb:mem:x,USER=SA,PASSWORD= m1.sql z2.sql a3.sql On Thu, Nov 17, 2022 at 1:12 PM Fred Toussi fredt@users.sourceforge.net wrote: In the meantime, you should be able to use sqltool.jar version 2.4.1 with hsqldb.jar version 2.7.1 Issues upgrading to hsqldb and sqltool version from 2.4.1 to 2.7.1 https://sourceforge.net/p/hsqldb/discussion/73674/thread/f4a97d3670/?limit=25#02ee...
Confirmed. Please open a Bug ticket. Problem started > 2.4.1 and <= 2.5.1. Unrelated, when giving examples asking for assistance, you'll help more readily if you provide commands that others can easily re-use. In cases like this that would mean using a memory database, eliminating unnecessary quoting (which causes platform-specific difficulties), and use forward-slashes for file paths (even in classpaths).
As documented at https://search.maven.org/artifact/org.hsqldb/hsqldb/2.7.0/jar but add classifier with value "jdk8".
Merged trunk updates into tag 2.7.0. Could not use update-merge capability because svn server so old.
Fixed typo that broke build when attempting to update only comments. Thanks to report from Fred.
Updated publish instructions
Provisional mvn build file update to ultimately use Ant build targets as source for the Maven source jar files. Needs to be tested with publish tasks.
Published *javadoc*.jar files should now have correct content
Published *source*.jar files should now have correct content
Update to mvn-pub.gradle to support changes to lower-level build files
Satisfied most non-trivial cmdline code inspection warnings
Removed debug echo directives that I accidentally committed with rev 6513
Partial progress satisfying IntelliJ code inspector
Removed SecurityManager accommodation since SecurityManager deprecated
work-arounds for using same output class file for multiple input source files
fixed a mistake in build.xml
Addd comment of example property settings for a cross-build
Fixed in trunk (for Maven jars going forward) with commit 6448. To cross build for Java version x, set build properties ant.build.javac.target and javac.bootcp.override. For goal of target 8, we need the latter set to paths to the 8 rt.jar and jce.jar. Make sure to do a full clean (like with clean-all target/task) so nothing from previous build state gets used. I verified that a hsqldb.jar built this way works with Tobias's test setup. (Thanks for that).
Fixed in trunk (for Maven jars going forward) with commit 6448. To cross build for Java version x, set build properties ant.build.javac.target and javac.bootcp.override. For goal of target 8, we need the latter set to paths to the 8 rt.jar and jce.jar. I verified that a hsqldb.jar built this way works with Tobias's test setup. (Thanks for that).
Resolved cross-compile problem
Added error-handling from 2 exec tasks and 1 forked java task
Added diagnostics to DocBook schematron invocation
https://repo1.maven.org/maven2/org/hsqldb/hsqldb/2.6.1/hsqldb-2.6.1-jdk8.jar For dependency configs, use classifier "jdk8".
https://repo1.maven.org/maven2/org/hsqldb/hsqldb/2.6.1/hsqldb-2.6.1-jdk8.jar
Several \d commands working for SQL Server. \r not practical. \dS needs more work and for now is same as \dt. \dt, \dv, \dS just list the objects in the CURRENT database instead of properly differentiating system objects
All \d commands working for MariaDB
All \d commands working for MySQL
All \d commands working for Oracle
All \d commands now work for RedShift databases
All \d commands now work for Postgresql
Minor corrections re. MySQL/MariaDB intercompatibility, based on testing
Many updates. Now cover all AWS database variants.
Added test script re.inter for regexp command recall
Removed scripts build.gradle and runtests.bash because don't want to maintain them. Script runtests.groovy works great.
make interpreter line more portable
remove useless whitespace
As Fred was thinking, the problem is with the classpath in the sqltool jar manifest. You need to rename the hsqldb*.jar file to be either hsqldb-2.6.0.jar or hsqldb.jar. Doesn't matter what the sqltool jar is named as long as you give the path to it in your invocation. (You can rename it to something else entirely if you wish to). If you ever have any doubt about what hsqldb file names it honors, take a peek at the jar MANIFEST.MF file. Here's a Bash function to conveniently see the manifest without...
Will be working on this over the weekend. Thanks for the input. On Fri, Apr 9, 2021 at 3:33 PM Iwao AVE! kforkiss@users.sourceforge.net wrote: Hello, The current binary requires JDK 11. https://repo1.maven.org/maven2/org/hsqldb/hsqldb/2.6.0/ It would be difficult to add JDK-8 version to 2.6.0, so please consider it when you release future versions. Thanks in advance! Iwao Please publish JDK 8 compatible binary on Maven Central https://sourceforge.net/p/hsqldb/discussion/73674/thread/3cef74552d/?limit=25#26e6...
To accommodate evolving Linux conventions, updated default hsqldb.conf file for Linux, but still honor legacy locations
Updated default pid file location, to prevent warnings fro modern Linuxes which prefer /run
Updated default pid file location, to prevent warnings fro modern Linuxes which prefer /run
Removed spurious log-level mapping. Non-functional change since bad mapping always got replace.
Removed references to external docs that I no longer want to maintain
Fixed Jflex tt replacement. Must be done to src/... file not the switched-src file.
Added Sealed attribute (true) to jar files
Replace deprecated <tt> tags in Jflex generated source file
Evolved build sequence allows for Servlet class inside modular hsqldb.jar
module build of hsqldbmin.jar
fix mistake
Optimized sqltool module descriptor based on jdeps generation
Added JDBC service module definition to org.hsqldb module descriptor
Disable legacy JDBC driver class load from RCData
sqltool module.info descriptor tested in apps
Moved class org.hsqldb.lib.RCData to org.hsqldb.util.RCData
When Gradle loads build.xml remove ant-specific target 'help'
Cloned FrameworkLogger class now works when both are loaded
Update to accommodate move of 'logging.properties' file with JRE 9
Removed malformatted and unnecessary entry from sqltool manifest class-path
Increment version to 2.5.2
Can now build both sqltool and hsqldb jars in a single run
Set jar main-class in a way that works both for classpath and modular executions
Fixes to SqlTool build to accommodate generalization of previous commit
Removed duplicate target -module_info; reworked classes and classes-base targets since descriptor compile must be value-parameterized but call-by-dep-attr doesn't support runtime value-parameterization; generalized target hsqldb and eliminated target hsqldbmodule
Generalized Ant target '-sqltool-mdescriptor' to '-compile-mdescriptor'
SqlTool now builds correctly for pre-9 or post-9, switching automatically
Code changes required for modular build of SqlTool
Partial provisional code for cloning shared subset of library source files for SqlTool
Moved module descriptor source for module org.hsqldb to home under src/modules branch
Configured Gradle task 'tasks' to display what we want, eliminating task 'hsqltasks'
build simplifications
fix comment for javadoc
fix minor typo
Tag for Gradle upgraded to 6.7.1
Upgraded Gradle to v. 6.7.1
Nothing here is exposed from the database, as the values being reported on are invalid values that haven't even been presented to the database. There is exposure to the client JVM, but exposure of two things that are already available to the client JVM. Everything done in RCData is client side, so anybody who has access to the JVM gets no more visibility than they already had. If you are concerned about exposure to outside of the JVM by the exception displaying to stderr, that isn't controlled by...
Nothing here is exposed from the database, as the values being reported on are invalid values that haven't even been presented to the database. There is exposure to the client JVM, but exposure of two things that are already available to the client JVM. Everything done in RCData is client side, so anybody who has access to the JVM gets no more visibility than they already had. If you are concerned about exposure to outside of the JVM by the exception displaying to stderr, that isn't controlled by...
NodeJS has multiple packages for accessing JDBC databases. From browser engines may be possible to route through AJAX using HSQLDB http proxy protocol but would probably be considerable to work to marshal and unmarshal the payloads.
Tested behavior. Ran SqlTool regression tests. Committed patch to base/trunk with rev. 6168. Thanks.
Applied patch from ticket #1588 by Jesse Pavel
Ty. It will be some days until I'll be able to test this. In case I see different behavior, what JRE are you using?
Please confirm that the problem is with regular forward slashes within filepaths, not backslashes. Please paste the error message or indication.
Updated examples of build classifier specifications
Release tag for 2.5.1
Exclude module-info.java from javadocdev target because it breaks it
updated readme timestamp to reflect release time
Updated SqlFile version