Some characters in files cause errors upon opening in EditorĭESC (F4)on non-existent DBLink resulted in application error Log switch frequency map seems to show the incorrect number of logs cut on Oracle RACĭatabase Monitor does not display statistics for a 10.1.x database Sort on the Tablespace window and exporting to an Excel file, corrupted dataĬreate Index Compute Stats option not added in with Bitmap option Not recognizing second node's alert log on a two-node 9i RAC Single Record View|Save|Favorites causes view to be brought to front, no focusīrowser does not populate LHS with entries that have HOST and PORT in lowercase Sorting a column after applying a custom filter to a different column loses filter Schema Browser List index out of bounds when sorting '.' button appears for BLOB columns in Data Grid Hitting CTRL-END twice in results grid hangs Toad Not all columns visible for mapping if file column names do not match table'sĭata Grid: Date error response (more user friendly message) View script creates 'alter table' command not 'alter view' for views with pk Rebuilding table leaves ON DELETE SET NULL option off foreign keys Loading Schema Compare scripts problems after upgradingĬompare schema with DBLInk and 'SQL*Plus 'prompt' comments in script' is invalid Table without supplemental logging listed as not existing Schema Compare showing differences when they should not be shown Resolved Issues ComponentĮrror when attempting to save addm.ini fileĪccess Violation in Action Palette when history is full Effectively as long as the ci can run tests for 1 legacy framework (probably 4.8) and 1 'core' version (6 or 7) and we can still build all target framework versions for publishing I'm in favour of being as close to the latest language features as possible.The following is a list of issues addressed and enhancements implemented in this release of Toad for Oracle. I'm in favour of adding newer version support too though.Īll that being said I'm not actually sure what of the past like 7 C# versions are restricted to which frameworks versus being dictated by language version versus ci runner. NET 3 versions is it gets painful to write in versions that early but by keeping the library dependency free, with the exception of valuetuple and being careful with syntax means the library will continue to support the unfortunate Devs maintaining these legacy apps.
The only reason I haven't gone back further to. Primarily I was working with government software that I'd be surprised if some instances have even reach NET 4 yet. A lot of these places are going to be running ancient versions and the migration paths off them are going to be long too, in the multiple years to bump the version. So the reason for the current target frameworks being excessively broad is based on my past experience in. Any opinion Happy to create the PR if need be 100% agree with might be good to update to dotnet 6.
0 kommentar(er)
