Revision History for AbaPerls – Details

This page lists all changes to the AbaPerls tools and documentation from the first public release L1.0.0009 and on. (OK, not all changes, but the level of detail is fairly high.) The horizontal lines divide external public releases from each other. For a compact history for the external releases, see this page.

2010-10-24

The seventh public release of AbaPerls,  label L1.0.0190.

2010-09-01

AbaPerls now supports table types and XML schema collections. They can be defined in the file types .TBLTYP and .XMLSC  respectively. These files resides in the TYPE directory. In DBBUILD and DBUPDGEN, XML schema collections are loaded before regular types (.TYP files), whereas table types are loaded after. You can also define a table type or an XML schema collection in a .SP or .SQLFUN file, if the type/schema is to be used by this procedure only. In this case the name must follow certain rules. See further in the section about the SP directory on the Structure page.

AbaPerls now supports CREATE TYPE to define type. EXEC sp_addtype is still supported.

You can now create an assembly directly through a source file written in C# or Visual Basic .Net. To do this, you need to supply the $COMPILE directive in the .ASSEM file. You find more information on the CLR page. As a consequence of this change, version-checks now also include .ASSEM files.

If you run DBBUILD -rebuild for a single subsystem, AbaPerls now clears the settings configuration settings only for that subsystem, and  leaves global settings and settings for other subsystems unchanged. Note also that the subsystem is rebuilt using the global configuration settings.

When you had expressions with .nodes(), AbaPerls could produce a internal error about too many iterations. This problem has been fixed.

I'm doing a minor overhaul of the design of the manual pages, and in a transitional period, the design between different pages will vary.

2010-05-25

ABASQL now masks any password when printing the command-line options.

2010-04-28

Added two new macros $DBPERM and $SERVERPERM that permits you to encapsulate permissions that can not be handled with regular ownership chaining. Examples include use of dynamic SQL and BULK INSERT. See the new topic Modules with Special Permissions for more details.

Added an argument to the $DLLINCLUDE macro where you can specify the permission set for the assembly. Using this directive, you can install unsafe assemblies on databases that are not marked as trustworthy. See the topic Privileged Assemblies on the CLR page for details.

2010-03-23

Fixed bug in RUNSPS which caused RUNSPS to loop indefinitely if you did not supply any parameter definition at all, for instance because the procedure does not have any.

2010-03-03

Added the option -tablesfirst to DBBUILD. This option specifies an alternate build order where tables and views in all subsystem are built before any functions or procedures are loaded.

Augmented the AbaPerls file-lookup order, so that AbaPerls now looks for the file in a subsystem directory before trying a an AbaPerls SQL directory structure on the same level.

2010-02-26

AbaPerls now supports use of WHERE clauses in the definition of index and statistics, so-called filtered indexes.

2009-11-25

RUNSPS is now able to read regular Excel books, and is not constraint to CSV files. Older CSV files still work with RUNSPS, as long as Excel can read them.

2009-05-18

DBBUILD and DOBCP now use the -q option with BCP to set the setting QUOTED_IDENTIFIER (which for some reason is not on by default with BCP.)

2009-02-09

DBUPDGEN no longer complains if the -VSS option disagrees with the project in the file, if the only difference is that one of them has /SQL and the other not.

2009-01-02

The sixth public release of AbaPerls, label L1.0.0091.

The tool PREPRC has been dropped.

2008-11-12

Fixed bug in aba_check_column, so that it now correctly returns 0 when -noexec is in effect.

2008-10-13

DBUPDGEN now generate update scripts that sets an error status on DOS level (i.e. %ERRORLEVEL%) if there are objects with names starting in old_ before the update starts, or when the update has completed.

2008-08-26

The rules for ABASQL in the version-check in the AbaPerls file-loading process have been modified. Previously AbaPerls required that when a file was loaded from SourceSafe that the path was the same as when the file was most recently loaded. This has been changed so that the check is now performed against the SourceSafe path the subsystem was most recently loaded from. The check is only effective if the ABAPERLS subsystem in the database is upgraded to label L1.0.0081. For older versions of the ABAPERLS subsystem, the old version check is retained.

2008-07-29

• The default for the config-options -Anulls and -Apadding have changed, so that ANSI_NULLS and ANSI_PADDING are on by default.
• The type ap_scriptname is now defined as varchar(64) to permit for longer script names to be stored.
• A new predfined macro: &SQL2008.

Important note: to get the updated version of ap_scriptname, you need to run an update script, ap_up_1-0052-0080.pl. However, this script does not run on SQL 2005 RTM and SP1. The script runs on SQL 2000 and earler, SQL 2005 SP2 and SQL 2008. The reason is that sp_rename SQL 2005 RTM/SP1 checks for referencing stored procedures when you rename a type, and ap_scriptname is used by the procedure that loads objects into abasysobjects, resulting in a catch-22 situation.

2008-03-18

ABASQL now requires that you specify -subsystem also for .TBL files. (As failing to do so when you create the table the first time, could buy problems further down the road.)

2008-03-10

INSFILGEN used to insert an extra go after each 40th call. This has been removed. (It was a workaround for problems with the tools in SQL 6.5)

2008-03-05

Added support for synonyms. See the page Using Synonyms for details.

2008-03-02

Bugfix: it was not possible to connect with AbaPerls to databases with space or other special characters in the name.

2008-02-03

Because of changes in SQL 2005 SP2, LISTERRS failed to list calls to missing stored procedure. This has been fixed. Also, AbaPerls also correctly handles the same situations with SQL 2008.

2008-01-12

The fifth external release, L1.0.0060.

When using SourceSafe 2005, DBUPDGEN could crash while reading the object histories. This has been addressed.

AbaPerls is now able to understand Common Table Expressions (CTEs). Support for the MERGE statement in SQL 2008 added.

2008-01-01

There was a problem with SourceSafe that made it impossible to dates with -label in various tools with SourceSafe 2005. AbaPerls now has a workaround for this problem.

It is now possible to use the @ character as separator for site-specific files as an alternate to % which has been outlawed by SourceSafe since 6.0d.

2007-09-17

ABASQL now has the options -noexec and -get, and ABASQL is now able to read SourceSafe information from SS-FILES.LIS, permitting using ABASQL to install files at customer sites to which you have no direct connection.

2007-08-30

AbaPerls no longer performs object checking for the pattern ident1.ident2.ident3(. Previously, AbaPerls attempted to verify this as a scalar user-defined function with the database part of the name included. However, in SQL 2005, there is no syntactical difference between the call to a UDF and the invocation of a type method of an XML or CLR UDT column. AbaPerls opts to validate two-part names, but not three-part names, that looks like function calls. As a consequence of this, you need to always use a table or alias prefix with your XML and CLR UDT column when you  need to invoke a method, for instance t.item.value().

A similar issue with the table-valued XML method .nodes has also been addressed. AbaPerls ignores three-part names that ends in nodes and are followed by a right parenthensis.

There was a bug with object checking, so that AbaPerls did not see a scalar function when it appear directly after a keyword. This bug has been fixed.

2007-08-15

Thanks to Koen de Vos, the update scripts generated by DBUPDGEN will now correctly transfer ON DELETE/UPDATE CASCDE and also NOT FOR REPLICATION when moving foreign keys from one table to another.

2007-06-05

DBBUILD and the update scripts generated by DBUPDGEN now accepts an option -User to permit you to specify a different SQL login than sa. AbaPerls verifies that the login you use – SQL login or Windows login – has dbo as the default schema. This applies to ABASQL as well.

DBBUILD and the update scripts generated by DBUPDGEN no longer sets the database in simple recovery, nor do they set a read-only database in read-write mode, but you need to cater for this yourself. As a consequence of this, the update scripts are no longer generated with the -trunctrue option.

2007-05-21

DBBUILD now uses the option -h "CHECK_CONSTRAINTS" with BCP to make sure that constraints trusted. Also added the utility procedure ap_zz_enable_constraints_sp to enable all constraints in a database. Added a note the page for DOBCP about constraint checking.

2006-11-20

• There were big holes in the version checks for production and test databases, so that an object could be over-written by an older version when it shouldn't. There were also a situations when a file was not loaded when it should. All these problems were related to $REQUIRE. The file included with $REQUIRE was not checked in itself and was stored in abasysobjects without subsystem in the object name. This has been addressed.
• Preppis now only permits you to use $INCLUDE from certain file types, and the target for $INCLUDE must be an .SQLINC file. Likewise $REQUIRE can only be performed on the file types .SQL, .POSTSQL, .ASSEM, .INC, .VIEW and .SQLFUN, and $REQUIRE is only permitted from a file of the same type. The reason for this restriction is to avoid surprises with update scripts for unusual cases that have not been properly analysed.
• ABASQL no longer runs files loaded by $REQUIRE, but only reads them to check that $USEDBY is present. This to avoid that an older version of a file over-writes a newer.
• ABASQL now prints the current label of the AbaPerls installation.
• DBUPDGEN now reads all changed files that can include a $USEDBY, and adds the referring files to the update script. Previously, DBUPDGEN only did this for include-files and assembly files.
• Previously, -force permitted you to override the check between file name and object name for any type of object. You can now only override this check for stored procedures and user-defined functions.
• Previously, -force permitted you to override the check that the object agreed with the file type, so you could for instance create a stored procedure from a .SQLFUN file. This possibility has been removed.
• There is now a check that a file that is supposed to define objects (for instance an .SP file) also does this. If such a file does not define any objects. This check does not include comments and code that was removed by $IF/$IFDEF macros.

2006-10-27

• AbaPerls now uses a different client API, Win32::SqlServer This means that you must download and install Win32::SqlServerto be able to use AbaPerls.
• AbaPerls now includes support for CLR assemblies. See the new page Using the CLR with AbaPerls for details.
• LISTERRS failed to display errors that occurred when bulk-loading data. This problem has been fixed.
• DBBUILD will now use format files if available when you use the -bcp option.
• AbaPerls permitted two objects of  differerent types to have the same name. For instance, you could have both a stored procedure and an index named nisse. This resulted in confusing information in abasysobjects. The AbaPerls file-loading process now checks for name clashes between object types.
• When a file included a $USEDBY directive for a file not found in the current system, DBUPDGEN nevertheless added the non-existing file to the update script. This problem has been fixed.
• There is a new predefined macro for Preppis: &SQL2005. (And the page for Preppis has been corrected. It listed &SQL8 as a predefined macro, but the correct name is &SQL2000.)
• The directive $TABLE has been removed from the Preppis page. I realised that it would never be able to play with the DBBUILD load order, so I will have to think of something better.
• I've added a documentation note on how to refer to server instances with port number. You need to use quotes, to prevent the comma from being intercepted by the command-line module that I use. For instance -S "127.0.0.1,2093".

2006-10-19

The tool SPTRITEST has been removed. It was a useful tool on SQL 6.5, but less so on later versions.

2006-10-18

Changes to DOBCP:

• -native is now default.
• DOBCP now by default uses format files. When you specify out, DOBCP automatically generates format files. When you import data, DOBCP by default assumes that there is a format file for each table. -nofmtfile instructs DOBCP to not use format files.
• New option -unicode to force Unicode format for all character data. The default is -nounicode.
• The option -421 has been dropped.

2006-09-20

• Added new file type .POSTSQL in the MESSAGE directory. DBBUILD runs these file last in a build.
• DBUPDGEN now puts .SQL files in the MESSAGE directory first in the update script. .POSTSQL files ends up where the MESSAGE section use to be.
• The AbaPerls file-loading process now supports the Service Broker statements BEGIN DIALOG and SEND and checks for missing services, contracts, queues and message types.

2006-08-25

AbaPerls now reads the real SRCSAFE.INI for the SourceSafe database, and if there is a definition of a journal file, it is copied to the SRCSAFE.INI that AbaPerls creates so that actions from tools like SSREPLACE and NEWSUBSYSVER are journaled appropriately.

2006-02-17

New feature in update scripts from DBUPDGEN: you can now have a final epilogue.

2005-12-28

• The database part of AbaPerls now performs checks that the client version is not behind the version of the database.
• New configuration option -environment, permits you to classify a database as development, test or production database. For test and production databases, the AbaPerls file-loading process performs checks to avoid that update scripts over-writes newer versions. This also enforces rules when you load files with ABASQL. See the file-load page for details.
• In abasysobjects, the object name for object-less files (save include-files) is subsystem!filename, so AbaPerls can track files from different subsystems with the same name. The update script to L1.0.0042, updates abasysobjects with the information from abahistsysobjects, as far as this is possible.
• It is now compulsory to specify a subsystem when you load object-less files (that insert-files and the like).
• When you load a file with ABASQL without specifying a subsystem, ABASQL no longer sets the subsystem to NULL in abasysobjects for existing files, but retains the value previously stored.
• Added check to disallow the EXECUTE AS clause for stored procedures in SQL 2005.
• The pages for the AbaPerls system tables, has a new design, as the data model now is maintained in PowerDesigner 9.5.
• PDREP95 now supports custom footers and now handles stored procedures views.

2005-12-05

Bugfix: ABASQL would incorrectly report file successfully loaded, when it in fact it could not even find the file in SourceSafe.

2005-10-28

LISTERRS now knows how to filter out messages about missing stored procedures that appear later in the script. As a consequence of this DBBUILD no longer by default loads stored procedures twice. There is a new option, -sptwice, to request this in case you want full dependency information. Note that this is only possible to achieve on SQL 2005, due to flaws in SQL 2000 and earlier versions.

2005-10-21

The Preppis directives $MACRO_LONG and $ENDMACRO are now implemented.

2005-10-13

New option for SSGREP, -crossref, that causes SSGREP to print matches per unique string. This is good if you are looking for references to a couple of stored procedures or similar.

2005-04-29

The AbaPerls File-Loading Process now also replaces user-defined data types in schema declarations for OPENXML.

2005-04-27

LISTERRS no longer prints headers for subsystems in which there are no errors.

2005-02-01

The AbaPerls File-Loading Process now also checks for improper comparisons with NULL, e.g. WHERE x = NULL.

2005-01-27

When generating an update script, DBUPDGEN did not add code SET IDENTITY_INSERT ON, if the IDENTITY keyword followed NOT NULL in the table definition. This has been fixed.

2005-01-19

Several checks added/enhanced for the AbaPerls File-Loading Process:

• AbaPerls now checks for old-style outer join (*= and =*) and emits an error or a warning, depending on the tool in use.
• AbaPerls now checks performs that you use WITH for table hints where SQL 2005 requres this.
• Previously AbaPerls emitted warnings for missing objects. Under normal circumstances, AbaPerls will not emit a error for this condition.
• AbaPerls now calls it an error if the name of an object does not agree with the file name, or the type of the object does not agree with the the file extension. This can be overridden with the -force option.

2005-01-14

Added -log option to ABASQL.

2005-01-03

New tool PDREP95 for handling of reports generated by PowerDesigner 9.5.

2004-10-31

The fourth public release, L1.0.0040.

2004-09-10

• AbaPerls now checks for name-clashes between subsystem. If subsystem A has defined some_sp, subsystem B is not permitted to use that name. (This can be turned off in an update-script, but not elsewhere.)
• AbaPerls now supports that referring subsystems add their own triggers, index and foreign keys to tables defined by lower subsystems. (The big thing here is triggers, the other two are for consistency.) Previously, AbaPerls dropped all triggers, indexes or foreign keys for a table when you loaded such a file. Now AbaPerls only drops those in the current subsystem. Be aware that when you run a table-update, the triggers, f-keys and indexes in referring subsystems will have to be reloaded. To make this a little easier, DBUPDGEN always include .TRI, .FKEY and .IX files in update scripts, if there is no matching tables.
• As a consequence of this change, it is now mandatory to provide -subsystem to ABASQL when you load triggers, indexes and foreign keys.

See more about this on the pages for the, AbaPerls structure, the file-loading process, DBUPDGEN and ABASQL.

2004-07-08

Slight change in the table-updates generated by DBUPDGEN: there is now a variable $batchcol which makes a little easier to change the control column for the INSERT-loop.

2004-07-06

Two options for SSGREP and SSREPLACE: -type and -lang that you can use to constrain the tools to only work with files of certain types. For instance -lang SQL will constraint the search to SQL files.

2004-07-05

The AbaPerls file-loading process could incorrectly gave a style message for a computed column.

In the update scripts generated by DBUPDGEN, the table-updates now use RAISERROR WITH NOWAIT to print their messages, so that they are flushed to the log immediately. The first message for a table-update, which displays the number of rows to copy uses severity level 8, so that you can use LISTERRS to review the copying.

2004-05-19

LISTERRS now supports reading logs from update scripts generated by DBUPDGEN. To this end, there are some minor changes to the logs from DBBUILD and the update scripts.

INSFILGEN and LANGINSGEN now wants to you declare maximum lengths for parameters with string data, to avoid truncation when you run the INSERT-files. You declare these lengths in a MAXLEN section on the Config sheet. To begin with MAXLEN is not mandatory, but the plan is that it will eventually be.See further the INSFILGEN page.

2004-05-07

TBLFIX now formats computed columns nicely.

2004-05-03

The third public release, L1.0.0030.

2004-05-02

New features

• AbaPerls now supports indexes and triggers and views. For these objects, use the file extentions .VIX and .VTRI respective. The files should reside in the VIEW directory in the AbaPerls SQL Directory Structure, and the name should be the name of the view.
• AbaPerls now supports the command CREATE STATISTICS. You put statistics in the same files as indexes, that is files with the type .IX or .VIX.

Changes:

• DBBUILD -rebuild now also reloads index files, both for tables and for views.

Bugfixes:

• The check in the AbaPerls file-loading process that object matched file name and file type, incorrectly checked an object in an included file against the main file.
• DBBUILD: If the new database contains rules and defaults, DBBUILD was supposed to drop these, just like it drop types but failed to do so. This problem has been corrected.
• When reading a config-file, AbaPerls failed to observe options for a subsystem that was on lines following the subsystem definiton. (This bug was introduced with the changes 2004-02-17.)
• The AbaPerls File-loading process did not seem to be able to cope with index definitions with a WITH clause at all. Either you would get a syntax error, or AbaPerls would silently fail to load the index at all. Now things works a little better: the index will be created if you place WITH on the same line as the closing parenthesis of the column list. If you place WITH on a new line, you will get a new syntax error. The applies to statistiscs definitions.

2004-04-28

When running AbaPerls with Perl 5.8.3 (or ActivePerl Build 809), you could get a run-time error in Perl just as ABASQL and similar tools were about to exit. I believe the cause is a bug in Perl, but a workaround is now in place.

2004-03-31

Bugfix in ap_sob_update_sp. When running an update script with name longer than 35 characters, the script failed with "binary or string data would be terminated". This has been fixed, so that the name is truncated to 35 characters when saved in abasubsystems. Since the change is in the stored procedure, you need to deploy this procedure to take benefit of the fix.

2004-02-17

Changes in DBBUILD:

• New command-line option -[no]insert permits you specify whether INSERT-files are to be loaded, independently of the -bcp option. Thus, you can now load both INSERT-files and BCP files in the same build. Default is -insert, unless you specify -bcp, in which case -noinsert is the default.
• Fixed bug that caused DBBUILD to give incorrect warnings for missing objects in other databases.

2004-02-11

Changes in DBUPDGEN and for update scripts generated by DBUPDGEN:

• New utility function aba_check_column() permits to easily check whether a table-update may have been run by a previous update.
• Temp tables to carry out the data-move of a table-update could refer to user-defined datatypes, which may not exist in tempdb, due to the changes from 2003-11-22. This is now fixed by calling a new function abasqltempobject which performs the pieces of the AbaPerls file-loading process that is relevant for temp table.
• New utitility routine aba_tblfkey2() as alternative for foreign-key moves in table-updates. See point 4 in the comments to the sample script.
• Fixed bug which case files to be included a second time, if they included uppercase characters.

2004-01-30

LANGINSGEN now supports multi-column keys.

2004-01-28

When using a config-file, and searching for the labels of the projects in the file where there is no explicit version-designator, the default behaviour of AbaPerls is now to consider only labels that match the standard AbaPerls label format LetterMajor.Middle.Minor. To permit you to override this behaviour, there are two new configuration options, -onlylabel and -notlabel.

2003-12-14

Bugfix: When DBUPDGEN was reading a table definition to generate a table-update, it failed to recognize CREATE TABLE if these words were in lowercase.

2003-11-22

Big news for the AbaPerls file-loading process:

• AbaPerls now replaces user-defined data types with their defintions in temp tables and table variables, and thereby relieving you of the need to have user-defined data types in the tempdb and model databases. As a consequence of this, DBBUILD no longer loads user-defined data types in these databases, and neither does  DBUPDGEN generate code for loading types in tempdb and model.

• AbaPerls now adds a COLLATE clause for all character (char, varchar, nchar, nvarchar, text and ntext) columns in temp tables and table variables for the default collation of the database. This permits you to mix databases with different collations on the same server, and freely move a database from server to another, without thinking of collations issues. (Obviously, to take benefit of this change you need run DBBUILD -rebuild for the database.) See the file-load page for an example.

• AbaPerls now checks that the objects in a file agrees with the name of the and issues a warning, if they do not. Likewise, AbaPerls issues a warning if a file contains an object which does not match with the file extension according to the AbaPerls SQL Directory Structure.

• The saved SQL files for ABASQL, DBBUILD and the update scripts generated by DBUPDGEN no longer includes the database name.

2003-10-01

Object checking now also finds objects in other databases, albeit still with some restrictions. See Known Issues for details. You need to install the user defined function list_to_tbl and stored procedure ap_check_existance_sp in the database for the improved checking to work. Else object checking will revert to the old behaviour.

2003-08-15

INSFILGEN: Added property Postlude to the Config sheet.

2003-08-12

New tool NEWSUBSYSVER that packages the procedure to create new version-subprojects.

2003-07-03

During file-load, AbaPerls now creates a temp table #current$subsystem(subsystem varchar(80) NULL) which holds the name of the current subsystem.

When DBUPDGEN generates code for a table-update, it now adds check that the number of rows in the new table is the same as in the old table. See further the section on table updates in the article on DBUPDGEN.

Fixed header generated by INSFILGEN, so that it does not include entry from check-in of INSFILGEN itself.

2003-04-21

The second public release of AbaPerls, L1.0.0021. The changes down to 2003-11-03 are the changes since first public release. Pay particular attention to the changes 2003-01-22 and 2002-12-05, since they include significant functional changes.

2003-04-11

The -crypt option did not work properly when you used the keywords AFTER or INSTEAD OF in a trigger declaration.

2003-04-10

If a table file had been renamed, DBUPDGEN did not include that file in OBSOLETE-FILES. This had the effect that the objects in the file were not deleted from abasubsystems. Note that if a file is renamed, but the objects are not, this could lead to that the objects are dropped from the database entirely, if the file is loaded in a table-update that appears before OBSOLETE-FILES.

2003-04-05

Documentation fix: if there is a site-specific version of a file, and the main file changes, DBUPDGEN includes all the site-specific versions in the file. This is not a new feature, but the page for DBUPDGEN failed to mention this.

2003-04-04

• Missing NOT NULL is no longer giving style message for an IDENTITY column, as IDENTITY implies NOT NULL.
• If the same temp-table name appeared twice or more in the same file, AbaPerls would try to create the table equally many times prior to running the file in the prework section, which would result in an error. AbaPerls now only runs the first CREATE TABLE/SELECT INTO statement it finds for the same temp-table name in a file.

2003-02-06

The update scripts generated by DBUPDGEN now creates a temp table #update$script that you can test for in triggers, to disable parts of the triggers when running an update script. Use it like this:

   IF object_id('tempdb..#update$script') IS NULL

2003-01-22

Database changes

There are several changes to the AbaPerls system tables. The main purpose of the changes is to permit two subsystems to have labels with the same Major, Middle and Minor, but have different letter and/or leading zeroes.

The new column abasubsystems.sortorder permits you define a sort order to that you can view abasubsystems and get the same order as in the config-file.

Other database changes are mainly of internal nature. See the database documentation for details.

To update the ABAPERLS subsystem to the new format, run the script ap_update_1.0.0020.pl which is in the SQL/SCRIPTS directory of the AbaPerls installation. You run this script as you run any other update script generated by DBUPDGEN.

The database update is not mandatory; that is, the tools will run against both the old format of the database (L1.0.0010) and the new format (L1.0.0020.)

Bug fixes

• There was a bug in ABASQL which caused space rather than NULL to be written to the subsystem column in abasysobjects and abahistsysobjects when you did not specify a subsystem.
• Under unknown circumstances, AbaPerls fails to find to a version number for a version-subproject. This caused DBUPDGEN to generate incorrect to Perl code. This problem in  DBUPDGEN has been addressed.
• If you fed DBBUILD a label which does not adhere to the LetterMajor.Middle.Minor format, DBBUILD would build the subsystem, and you would get an error at the end. DBBUILD now checks the labels before commencing the build.
• When using the -HTML switch with SSGREP, SSGREP did not escape characters such as <. > and &, that have a specific meaning in HTML. The same problem still exists in SSREPLACE.

2003-01-14

2002-12-27

• You can now specify macros in the cells in the Macros and Values sheet. They are combined with the macros for the columns. This permits you to have different settings in test and production for a customer.
• Included LANGINSGEN in INSFILGEN. LANGINSGEN is not included in the external distribution of AbaPerls, but for internal use at Abaris only.

2002-12-23

2002-12-17

2002-12-05

New or changed features

• Four new configuration options – -Adefaults, -Anulls, -Apadding and -Aquoted – permit you to control the ANSI-related settings. By default all such settings are on, except ANSI_NULLS and ANSI_PADDING.
• One new configuration option -quoterepl which causes AbaPerls to replace double quotes with single quotes as string delimiters before passing the code to SQL Sever. It is on by default.
• AbaPerls now emits SET commands to control its environment. Some of them are controllable by configuration options (see item above), others not. See further Emitting SET commands.
• DBBUILD and the update scripts generated by DBUPDGEN now writes a header for each subsystem to the log file. The header includes information about the settings of configuration options were in effect for that subsystem. The header information is displayed by LISTERRS.
• There is now an environment variable, ABAPERLS_CTIMEOUT that controls how long AbaPerls waits for a connection to SQL Server. The default is 5 seconds.
• AbaPerls now makes a half-hearted attempt to support identifiers quoted by [] or "", but there are still many situations where this does not work. See this known issue for details.
• Pre-SQL Analysis no longer handles sp_addmessage. Instead add the parameter @replace to your calls to sp_addmessage. See Books Online for details.

Database changes

• The column abainstallinfo.ss_db is now varchar(30).
• New values added to abaconfigproperties for the new configuration options. If you run the new version of AbaPerls against an old AbaPerls database, AbaPerls will add the new properties automatically.

Compatibility issues

• By default AbaPerls now runs with all SET commands required for indexed views in effect, but ANSI_NULLS and ANSI_PADDING. (Beware of that they may also be ON by default in a future version of AbaPerls.) The effect of QUOTED_IDENTIFIER being ON, is largely neutralized by the new configuration option -quoterepl also being on by default. However, if you have dynamic SQL strings like this:

     EXEC ('SELECT "Ciao!"') 

  That is, the inner string is delimited by double quotes. This statement will fail if it appears in a stored procedure that was loaded with the default settings in AbaPerls. Flipping quote style remedies the problem. This is further discussed under the -quoterepl option.

Documentation issues

• The page for the utility procedure ap_sub_rename_sp was missing.
• The description of configuration options has been moved to a page of its own. This page also includes what used to be called "config-option rules", now called "precedence rules".

Bug fixes

• When AbaPerls stripped the code of comments and later restored the comments, under some circumstances the restored comments incorrectly encompassed text that originally was not part of the comments. This bug affected the AbaPerls file-loading process and SSREPLACE.
• When using the -get option with DBBUILD and the update scripts generated by DBUPDGEN, the file was not fetched from SourceSafe, if it already was on disk, even if this was a different version than the one that should be in the install kit.
• If you specified -label LATEST to DBBUILD, the first configuration option for a subsystem was ignored, if it was on the same line as the subsystem definition.
• DBBUILD: if the directory for the BCP files included a space in the path, the BCP command was incorrect, because the filename for the BCP file was not quoted.
• DBUPDGEN could leave temporary files with type definitions around.
• DBBUILD: in some cases the -subscriber option in the database was ignored, and the command-line took precedence.
• When composing an update script for many subsystems, DBUPDGEN only wrote the name of one of the into the file header.

2002-11-04

The header is included in the output from LISTERRS

2002-11-03

First public release of AbaPerls.

Copyright © 1996-2010, Erland Sommarskog SQL-Konsult AB.
All rights reserved. AbaPerls is available under Perl Artistic License
This page last updated 10-10-24 22:45