ViewVC Help
View File | Revision Log | Show Annotations | Download File | View Changeset | Root Listing
root/public/ibx/trunk/changelog
(Generate patch)

Comparing ibx/trunk/changelog (file contents):
Revision 106 by tony, Thu Jan 18 14:37:35 2018 UTC vs.
Revision 107 by tony, Thu Jan 18 14:37:40 2018 UTC

# Line 1 | Line 1
1 < IBX Change Log  version                                   (2.1-1) Fri, 12 Jan 2018 10:13:29 +0000
1 > IBX Change Log  version                                    (2.2-0) Mon, 15 Jan 2018 23:43:19 +0000
2  
3 < 1. IBExtract: Identity columns - add addition check for null column for generator name.
3 > 1. IBExtract: Identity columns - add additional check for null column for generator name.
4  
5   2. IBCustomDataSet: Insert and Modify (Update) queries now recognise and process SQL RETURNING clauses.
6     The main use for this is for Firebird 3 Identity columns (see IBXDocumentation 6.6.8 for further
7 <   information). Values returned as a result of executing an Insert or Update statement
8 <   replace existing values in the current row for each corresponding column.
7 >   information). However, this is also a very useful mechanism for returning updated computed by
8 >   column values. Values returned as a result of executing an Insert or Update statement
9 >   replace existing values in the current row for each corresponding column.
10 >
11 >   Previously, if a dataset's select query included read only (computed by) fields then
12 >   an automatic row refresh was performed after an insert or update query had been processed,
13 >   irrespective of the setting of the "ForcedUpdates" property. This has changed such
14 >   that an automatic refresh is no longer performed if an insert or update query contains
15 >   a returning clause that updates one or more fields on the current row. A full row
16 >   refresh is only performed if (a) ForcedRefresh is true or (b) the query does not return any
17 >   field values and the select query contains read only fields. Use of Insert/update
18 >   returning should be significantly more efficient than excuting a refresh query.
19 >
20 >   This behaviour change is intended to be backwards compatible and there should be no need to change
21 >   existing programs, other than to improve performance by using the new capability.
22 >
23 > 3. TIBTable: generated Insert and Update SQL now include a RETURNING clause for
24 >   any Computed By or Identity Columns. The IBTables example has been updated to
25 >   illustrate the computation of the employee Full Name on update.
26  
27 < 3. The InsertSQL property editor now shows Firebird 3 Identity columns separate from the Field List.
27 > 4. TIBTable: The GeneratorField property is now published.
28 >
29 > 5. The InsertSQL property editor now shows Firebird 3 Identity columns separate from the Field List.
30     When InsertSQL is generated, the Identity columns are not included in the list of values to
31     be inserted. A RETURNING clause is added to the insert statement to return the value of
32     each Identity column after the insert is executed.
33  
34 < 4. TIBGenerator: small performance improvement by not preparing query each time
35 <   a new number is generated.
34 > 6. The Modify Property Editor now generates Update SQL with Computed By fields in Update..Returning clause.
35 >   Similarly Insert Property Editor now generates Insert SQL with Computed By fields in
36 >   Insert..Returning clause.
37 >
38 > 7. TIBGenerator: small performance improvement by not preparing query each time
39 >   a new value is generated.
40  
41 < 5. TIBSQL: Free resources when transaction changed.
41 > 8. TIBSQL: Free resources when transaction changed - ensures new transaction is used.
42  
43 < 6. Property editor will now sync table name to a System Table when "Include System
43 > 9. Property editors will now sync table name to a System Table when "Include System
44     Tables" is selected and the query is for a System Table.
45  
46 < 7. Modify Property Editor now generates Update SQL with Computed By fields in Update..Returning clause.
47 <   Similarly Insert Property Editor now generates Insert SQL with Computed By fields in
48 <   Insert..Returning clause.
46 > 10. Minor Performance improvement to handling of Date/Time types in IBX datasets. Field
47 >    values are no longer converted to milliseconds from TDateTime and then back again
48 >    to TDateTime (the conversion to milliseconds is the default TDataset approach).
49 >
50 > 11. Property Editors handling of Stored Procedures.
51 >    * Select and Refresh: only show a list of stored procedures that return multiple rows (proc type 1) and
52 >      which have a non-empty list of output parameters (i.e. stored procedures that may be used in a select
53 >      query).
54 >    * Modify and Insert: only show a list of stored procedures that return at most a singleton row (proc type 2).
55 >
56 > 12. IBStoredProc: Now supports Firebird 3 Package Names. A new published property PackageName
57 >    can be used to select a package. If non-empty, the stored procedure name is
58 >    expected to be a stored procedure defined in the specified package and the
59 >    generated SQL will be as required for a stored procedure located in a package.
60 >
61 > 13. Select, Refresh, Insert, Modify, Delete and TIBSQL SQL Property Editors now include
62 >    a "Package Name" drop down box to allow selection of a Firebird 3 Package from
63 >    which a stored procedure can be selected. With no package name selected, non-package
64 >    stored procedures are listed.
65  
27 8. Minor Performance improvement to handling of Date/Time types in IBX datasets. Field
28   values are no longer converted to milliseconds from TDateTime and then back again
29   the TDateTime (the TDataset approach).
66  
67   IBX Change Log  version                            (2.1-0) Fri, 15 Dec 2017 12:20:11 +0000
68  

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines