HyperSQL Utilities Guide - 使用手册
需积分: 7 123 浏览量
更新于2024-07-30
收藏 377KB PDF 举报
"HyperSQL Utilities Guide"
这篇文档是《HyperSQL Utilities Guide》的摘要，由HSQLB Development Group、Blaine Simpson和Fred Toussi共同编撰。这份指南详细介绍了如何使用HyperSQL数据库的各种实用工具。HyperSQL（也称为HSQLDB）是一个开源的关系型数据库管理系统，它支持SQL标准并提供了多种实用工具来管理和操作数据库。
在文档中，提到了以下几个关键知识点：
1. **SqlTool**：SqlTool是HyperSQL提供的一种命令行工具，用于与数据库进行交互。它不仅用于执行SQL语句，还具备一些高级功能，如脚本执行、日志记录和数据加载等。
2. **Platform and SqlTool versions**：SqlTool适用于多种平台，文档涵盖了不同版本的兼容性信息，帮助用户确保在他们的操作系统上正确运行SqlTool。
3. **Recent Functional Changes**：这部分详细列出了SqlTool的最新功能改进和行为变化，对于升级到新版本的用户来说尤其重要，因为它可以帮助他们了解新版本中的新增特性和可能影响现有工作流程的改动。
4. **New Features**：新特性部分详细介绍了自上一版本以来添加的功能，这些可能是提高效率或解决特定问题的新工具或选项。
5. **Embedding**：SqlTool可以被嵌入到其他应用程序中，使得开发人员能够在自己的应用中集成数据库管理功能。文档说明了如何在应用中嵌入SqlTool以及处理非显示数据类型的问题。
6. **Desktop shortcuts**：为了方便用户，文档还讨论了如何创建桌面快捷方式，以便快速启动SqlTool。
7. **Loading sample data**：SqlTool支持加载样本数据，这对于测试、演示或学习数据库操作非常有用。这部分会指导用户如何加载这些样本数据。
8. **CLASSPATH Requirements**：使用SqlTool时，需要满足特定的CLASSPATH要求，文档解释了如何配置这个环境变量以确保SqlTool能正确识别和连接到数据库。
9. **Accessing older HSQLDB Databases**：如果用户需要访问旧版本的HyperSQL数据库，文档提供了相应的指导，帮助用户解决可能遇到的兼容性问题。
10. **App-specific Classes, Embedding, and non-HyperSQL Databases**：除了HyperSQL，SqlTool还支持其他类型的数据库，这部分说明了如何在应用中使用特定的类和嵌入式数据库。
11. **Distributing SqlTool with your Apps**：对于开发人员，将SqlTool与他们的应用程序一起分发是有用的，这部分讨论了如何做到这一点，包括客户端PC的设置和配置。
12. **RC File Authentication Setup**：SqlTool支持通过RC文件进行身份验证，这简化了在多数据库环境中的身份验证过程。文档提供了设置RC文件的步骤。
13. **Switching Data Sources**：用户可以通过简单的方式在不同的数据源之间切换，这在处理多个数据库项目时非常方便。
14. **Using Inline RCAuthentication**：除了RC文件，SqlTool还允许在命令行中直接输入认证信息。
15. **Logging**：日志记录功能使得跟踪和调试SqlTool的操作变得容易，文档中详细介绍了如何启用和配置日志记录。
16. **Interactive Usage** 和 **SqlTool Command-Line Editing**：这部分介绍了SqlTool的交互式使用模式，包括命令行编辑和历史记录功能，帮助用户更高效地在终端中工作。
《HyperSQL Utilities Guide》是一份详尽的文档，为用户提供了使用SqlTool与HyperSQL数据库进行交互的全面指南，涵盖了从基本操作到高级特性的方方面面。
SqlTool
2
as possible (in several cases, database-specific work-arounds are used to obtain the underlying data even though the
database doesn't provide metadata according to the JDBC specs). Unlike server-side language features, the same fea-
ture set works for any database server. Database access details may be supplied on the command line, but day-to-
day users will want to centralize JDBC connection details into a single, protected RC file. You can put connection
details (username, password, URL, and other optional settings) for scores of target databases into your RC file, then
connect to any of them whenever you want by just giving SqlTool the ID ("urlid") for that database. When you Execute
SqlTool interactively, it behaves by default exactly as you would want it to. If errors occur, you are given specific error
messages and you can decide whether to roll back your session. You can easily change this behavior to auto-commit,
exit-upon-error, etc., for the current session or for all interactive invocations. You can import or export delimiter-sep-
arated-value files. If you need to run a specific statement repeatedly, perhaps changing the WHERE clause each time,
it is very simple to define a macro.
When you Execute SqlTool with a SQL script, it also behaves by default exactly as you would want it to. If any error
is encountered, the connection will be rolled back, then SqlTool will exit with an error exit value. If you wish, you
can detect and handle error (or other) conditions yourself. For scripts expected to produce errors (like many scripts
provided by database vendors), you can have SqlTool continue-upon-error. For SQL script-writers, you will have
access to portable scripting features which you've had to live without until now. You can use variables set on the
command line or in your script. You can handle specific errors based on the output of SQL commands or of your
variables. You can chain SQL scripts, invoke external programs, dump data to files, use prepared statements, Finally,
you have a procedural language with if, foreach, while, continue, and break statements.
Platforms and SqlTool versions covered
SqlTool runs on any Java 1.5 or later platform. I know that SqlTool works well with Sun and OpenJDK JVMs. I haven't
run other vendors' JVMs in years (IBM, JRockit, etc.). As my use with OpenJDK proves that I don't depend on Sun-
specific classes, I expect it to work well with other (1.5-compatible) Java implementations.
SqlTool no longer writes any files without being explicitly instructed to. Therefore, it should work fine on read-only
systems, and you'll never have orphaned temp files left around.
The command-line examples in this chapter work as given on all platforms (if you substitute in a normalized path
in place of $HSQLDB_HOME), except where noted otherwise. When doing any significant command-line work on
Windows (especially shell scripting), you're better off to completely avoid paths with spaces or funny characters. If
you can't avoid it, use double-quotes and expect problems. As with any Java program, file or directory paths on the
command line after "java" can use forward slashes instead of back slashes (this goes for System properties and the
CLASSPATH variable too). I use forward slashes because they can be used consistently, and I don't have to contort
my fingers to type them :).
If you are using SqlTool from a HyperSQL distribution of version 1.8.x or earlier, you should use the documenta-
tion with that distribution, because this manual documents many new features, several significant changes to interac-
tive-only commands, and a few changes effecting backwards-compatibility (see next section about that). This docu-
ment is now updated for the current versions of SqlTool and SqlFile at the time I am writing this (versions 3406 and
3604 correspondingly-- SqlFile is the class which actually processes the SQL content for SqlTool). Therefore, if you
are using a version of SqlTool or SqlFile that is more than a couple revisions greater, you should find a newer version
of this document. (The imprecision is due to content-independent revision increments at build time, and the likelihood
of one or two behavior-independent bug fixes after public releases). The startup banner will report both versions when
you run SqlTool interactively. (Dotted version numbers of SqlTool and SqlFile definitely indicate ancient versions).
This guide covers SqlTool as bundled with HSQLDB after 1.8.x.
1
1
To reduce the time I will need to spend maintaining this document, in this chapter I am giving the path to the sample directory as it is in
HyperSQL 2.0.x distributions, namely, HSQLDB_HOME/sample. Users of HSQLDB before 2.0.x should translate these sample directory paths
to use HSQLDB_HOME/src/org/hsqldb/sample/....
剩余59页未读，继续阅读
2020-08-05 上传
2021-04-01 上传
2018-02-08 上传
2023-08-08 上传
2023-08-08 上传
2023-08-08 上传
2023-08-08 上传
2023-08-08 上传
折叠-smile
- 粉丝: 79
- 资源: 13
我的内容管理
展开
