Announcing SQLCMD Version 86.00 (2008-07-15) ============================================ This is a feature release, adding support for fully qualified table names in LOAD statements, including delimited identifiers. You can also specify HTML format for outputting tables - this will generate just the table (not the or or tags). The 85.01 release (not made public) made some build fixes for AIX, too. The 86.00 release also fixes a bug in the handling of LVARCHAR during LOAD that has been in the code for about a year - presumably, no-one loaded any LVARCHAR data during that time with SQLCMD. Finally, with version 86.00 I am releasing (somewhat minimal, but nevertheless quite effective) test suite. Look at the Test/SCHEDULE file to see what I thought should be a good set of tests, circa 1992. It would still be a good set of tests - it just needs some time spent on the implementation. Run 'make test' to run the tests. Build Changes ------------- The file previously called CONNECTY.c is now connecty.c.std (to avoid problems on machines with case-insensitive file systems). If you need to use it (you have no variant of Yacc available on the machine), run './configure' as before, then run 'make no-yacc' before running 'make'. This will rename the files for you, permitting the build to complete. This code was recently revalidated against a C++ compiler (G++ 4.2.3) and it compiles cleanly except for the warnings about an unused variable, kludge, in one file. The warnings are correct (kludge is unused). Packaging Changes ----------------- Starting with the 81.0x releases, the packaging process used to release SQLCMD now includes a file such as sqlcmd-82.03.sha, which contains the SHA-256 checksum (and file size) of each file in the official distribution. (The 81.0x releases used MD5 checksums, just to be pedantically accurate.) This can be used with a standard SHA-256 checksum generator to establish which, if any, of the source files have changed. The other files for which checksums are generated include the main source tar file. Contact me for the chksumtool Perl script I use to generate this information. A second change is that the software is given a public timestamp by http://publictimestamp.org/. The public timestamp includes many checksums (pretty much any algorithm you can think of and probably a fair few you didn't know existed) for the released tar files, and also establishes a date and time for when the code was released. You can also use the web site to validate that you obtained the correct software. You can also take, say, the SHA-256 checksum of a file you found on the internet and ask whether PublicTimeStamp.org knows which file it is. If it does, it will give you the metadata too. SHA-256 Checksums and File Sizes -------------------------------- SHA-256 a25d97c071c73a106b145a5210fb1ca08ba001b304b52a3fc48ee155530d25a6 1068143 sqlcmd-86.00-MSD.tgz SHA-256 0aef3a9ed49e34315ee3fa74318d9c7bdf9a1113e4a319709bb174d710fdec56 912701 sqlcmd-86.00-Master.tgz SHA-256 00e51c595b64bc9064d66b1e28121491ba3839916722ccecf3c01d36f870655c 97 sqlcmd-86.00.sum SHA-256 4892abed7e6b0fc72ced5caba9f6a74c488361b774697c4a54c0f00fb4bc046d 460959 sqlcmd-86.00.tgz Public Timestamp (PTS) Numbers ------------------------------ PTS#877143 sqlcmd-86.00.tgz PTS#877144 sqlcmd-86.00-MSD.tgz PTS#877147 sqlcmd-86.00-Master.tgz PTS#877149 sqlcmd-86.00.sum PTS#877150 sqlcmd-86.00.rel Jonathan Leffler Variously: jleffler@us.ibm.com, j.leffler@acm.org, jonathan.leffler@gmail.com