ViewVC Help

View File | Revision Log | Show Annotations | Download File | View Changeset | Root Listing

root/public/ibx/trunk/changelog

Comparing ibx/trunk/changelog (file contents):
Revision 104 by tony, Thu Jan 18 14:37:29 2018 UTC vs.
Revision 141 by tony, Thu Jan 25 14:18:12 2018 UTC

#	Line 1 | Line 1
1	<	IBX Change Log  version                                  (2.1-1) Sun, 07 Jan 2018 15:15:13 +0000
1	>	IBX Change Log  version                                              (2.2-0) Thu, 25 Jan 2018 13:56:39 +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 executing 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. IBCustomDataSet: DELETE...RETURNING queries are now also recognised. However, as
24	>	they are called when the dataset row is being deleted, there is no value in
25	>	updating the current record from the query result. Instead, a new event handler
26	>	"OnDeleteReturning" is provided. If a DELETE...RETURNING query is execute and
27	>	an OnDeleteReturning event handler is provided then it is called with the IResults returned
28	>	by the query. The event handler can then interrogate the query results and
29	>	perform whatever action is necessary. For example to confirm, to the user,
30	>	the deletion of a row with the returned values.
31	>
32	>	4. TIBTable: generated Insert and Update SQL now include a RETURNING clause for
33	>	any Computed By or Identity Columns. The IBTables example has been updated to
34	>	illustrate the computation of the employee Full Name on update.
35
36	<	3. The InsertSQL property editor now shows Firebird 3 Identity columns separate from the Field List.
36	>	5. TIBTable: The GeneratorField property is now published.
37	>
38	>	6. The InsertSQL property editor now shows Firebird 3 Identity columns separate from the Field List.
39		When InsertSQL is generated, the Identity columns are not included in the list of values to
40		be inserted. A RETURNING clause is added to the insert statement to return the value of
41		each Identity column after the insert is executed.
42
43	<	4. TIBGenerator: small performance improvement by not preparing query each time
44	<	a new number is generated.
43	>	7. The Modify Property Editor now generates Update SQL with Computed By fields in Update..Returning clause.
44	>	Similarly Insert Property Editor now generates Insert SQL with Computed By fields in
45	>	Insert..Returning clause.
46	>
47	>	8. TIBGenerator: small performance improvement by not preparing query each time
48	>	a new value is generated.
49	>
50	>	9. TIBSQL: Free resources when transaction changed - ensures new transaction is used.
51	>
52	>	10. Property editors will now sync table name to a System Table when "Include System
53	>	Tables" is selected and the query is for a System Table.
54	>
55	>	11. Minor Performance improvement to handling of Date/Time types in IBX datasets. Field
56	>	values are no longer converted to milliseconds from TDateTime and then back again
57	>	to TDateTime (the conversion to milliseconds is the default TDataset approach).
58	>
59	>	12. Property Editors handling of Stored Procedures.
60	>	* Select and Refresh: only show a list of stored procedures that return multiple rows (proc type 1) and
61	>	which have a non-empty list of output parameters (i.e. stored procedures that may be used in a select
62	>	query).
63	>	* Modify and Insert: only show a list of stored procedures that return at most a singleton row (proc type 2).
64	>
65	>	13. IBStoredProc: Now supports Firebird 3 Package Names. A new published property PackageName
66	>	can be used to select a package. If non-empty, the stored procedure name is
67	>	expected to be a stored procedure defined in the specified package and the
68	>	generated SQL will be as required for a stored procedure located in a package.
69	>
70	>	14. Select, Refresh, Insert, Modify, Delete and TIBSQL SQL Property Editors now include
71	>	a "Package Name" drop down box to allow selection of a Firebird 3 Package from
72	>	which a stored procedure can be selected. With no package name selected, non-package
73	>	stored procedures are listed.
74	>
75	>	15. TIBXScript: turn off database login prompt when reconnecting - this avoids prompting
76	>	for password on reconnect.
77	>
78	>	16. IBDatabase: use IAttachment for connection default character set id, code page
79	>	and character set name.
80	>
81	>	17. TIBDatabaseInfo: cache ODS Version information on first request in order to minimise
82	>	DB info lookups"
83	>
84	>	18. IBExtract: now supports DDL Triggers.
85	>
86	>	19. Add a property Editor for TIBUpdate.RefreshSQL.
87	>
88	>	20. IBUpdate: Ignore non-data (e.g. calculated) fields when assembling list of input
89	>	parameters. This stops an exception being raised when the field cannot be
90	>	located in the record buffer.
91	>
92	>	21. Property Editors now automatically include System Tables when opened and when the query table
93	>	is a System Table.
94	>
95	>	22. FB3UserManager example added to illustrate use if IBX for managing user logins, passwords
96	>	and connections using IBX and with single or multiple security databases.
97
18	–	5. TIBSQL: Free resources when transaction changed.
98
99		IBX Change Log  version                            (2.1-0) Fri, 15 Dec 2017 12:20:11 +0000
100

Diff Legend

–	Removed lines
+	Added lines
<	Changed lines
>	Changed lines