-
Notifications
You must be signed in to change notification settings - Fork 4
/
Releases
132 lines (109 loc) · 4.73 KB
/
Releases
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
Change Log:
1.1.13 2023-Oct
- Separate development schema module
- Better handling of binary data
- Handle language data better
- Better track data dictionary changes
- Better error tolerance
1.1.12 2023-Mar
- Parse metadata files written in yaml
- Break out development schema objects separately
- Enhanced language support
1.1.9 2023-Feb
- Connection crypto uses ECDSA algorithm
- Cache language data
- Bug fixes
1.1.5 2022-Sep
- Track with other packages
- New platform-independent wyseman client API
1.1.2 2022-Feb
- Works with production node-tcl release
- Misc cleanups
1.1.0 2022-Feb
- Port Wyseman CLI to JavaScript
- New JSON schema file format
- Mocha-based regression tests
- Schema migration capability
- Table save/restore scripts for testing
1.0.21 2021-Nov
- Update webpack and other dependencies
- Handle encrypted UI connection better
- Import/export encrypted connection keys
1.0.19 2021-Feb
- Restructure wyseman.js
- Separate connection code from command handler
- Add Node.js client module
1.0.18 2020-Apr
- Cleanups in preparation for versioning
- Persistently save table data on drop/restore
- Handle remote hosts
1.0.17 2020-Feb
- Retry if database not available
- Works with PostgreSQL 12
- Database dump/restore functions
- Wyseman can run properly with no DISPLAY
- Better isolation between websocket connections
- Improved grants/permissions
1.0.12 2019-Oct
- Work with permission improvements in wyselib
- Improved logging
- More secure validation checks on login
- Enhanced logic operators
- Login connection made as individual users
1.0.8 2019-Feb
- Support for authenticated login over SSL
- Initial login from ticket
- Subsequent logins from signed message from private key
- Add CLI utility for generating access tickets
1.0.0 2018-Dec Release 6: Node.js 1.0.0
- Run-time support added for javascript programs.
- Enhancements to support more robust Wylib data dictionary
- Initial support for a user-defined control layer
- Depending on the view, apps can access reports, previews, etc.
- License changed from GPL-3 to MIT
0.1.0 2017 Release 5: Resurrection
Ported main command line program to ruby. Package is a gem.
Also, after parsing the text files, the sql create/drop code is now
loaded into the database in a special schema area and sql queries
are used to produce the list of objects to rebuild given a certain
drop/create sequence.
There is still a TCL run-time library "wyseman" that can be called
from TCL apps to access the data dictionary. This is how the
bin/wysegi app still works. But there is now also a ruby run-time.
But when managing schema changes, TCL is now used only to parse the
schema description files. Ruby is the glue that holds the app
together. And most of the heavy lifting occurs right inside
Postgresql. For example, all schema items get dropped/rebuilt
in plpgsql so they are fully atomic. If your table restore fails,
the drop gets rolled back too!
0.40 2007? Release 4:
Changed to allow objects to be created in postgres namespaces
(schemas). Many changes were made to the wyseman system catalog
tables and columns. The interface for user programs should have
remained largely the same.
0.33? 2006? Release 3
Many bug fixes, many feature additions
0.32? 2005? Release 2
This release is updated for use with Postgres 8.1.0 which changed
fundamentally the way users and groups exist in the database.
Users and groups (roles) are now stored in the same table (pg_roles).
This shouldn't be a problem (as long as you avoid a username that
could be mistaken for a valid group name).
Postgres also changed the way sequences work. Typically you might
create a sequence and a table in association with each other. Some
field in the table will draw values from the sequence in order to
populate itself. Previously, wylib expected you to declare the
sequence as being dependent upon the table (since it was then
possible to create a table which referenced a non-existent sequence).
Then, we would populate the "create" field of the object with code
that would also initialize the sequence to a good number (like the
max value of the field that uses it). That way, you would build
the table, re-populate it with data, and then call the sequence
creation code to get it initialized to a value appropriate to the
pre-existing data in the table.
This is no longer possible, so you must now declare the table to
be dependent upon the sequence (so the sequences get built first).
Then, after restoring data to the table, execute a script that will
initialize the sequences to their proper values. This is shown in
the sample schema as "make sequence".
0.30 2004? Initial open-source release of version 0.30