You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+57-16Lines changed: 57 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,28 +17,34 @@ They appear in separate action view.
17
17
18
18

19
19
20
-
It behaves like Debug->Variables view, but no colorization (limitations of VS Code Extension framework) and automatically detects real type of `Node *` variables.
20
+
It behaves like Debug->Variables view, but no colorization (limitations of VS
21
+
Code Extension framework) and automatically detects real type of `Node *` variables.
21
22
22
23
Also, there are intrinsics for some types:
23
24
24
25
-`List` elements are displayed according their types
25
26
26
27

27
28
28
-
- Support for special members like `PlannerInfo->simple_rel_array` - array is displayed using it's length
29
+
- Support for special members like `PlannerInfo->simple_rel_array` - array is
30
+
displayed using it's length
29
31
30
32

31
33
32
-
Currently, there are 36 registered special members, but you can add your own using [pgsql_hacker_helper.json](#pgsql_hacker_helperjson) configuration file.
34
+
Currently, there are 36 registered special members, but you can add your own
35
+
using [pgsql_hacker_helper.json](#pgsql_hacker_helperjson) configuration file.
33
36
34
-
-`Bitmapset` elements with total lengths are displayed: `$elements$` - pseudo-member
37
+
-`Bitmapset` elements are displayed:
38
+
-`$elements$` - elements of set (array of integers)
39
+
-`$length$` - number of entries in set
35
40
36
41

37
42
38
43
### Dump `Node *` state to log
39
44
40
-
In PostgreSQL there is `pprint(Node *)` which dumps passed Node variable to stdout with pretty printing it.
41
-
Using 'Dump Node to log' option in variable context menu you also will be able to do so.
45
+
In PostgreSQL there is `pprint(Node *)` which dumps passed Node variable to
46
+
stdout with pretty printing it. Using 'Dump Node to log' option in variable
47
+
context menu you also will be able to do so.
42
48
43
49

44
50
@@ -47,9 +53,9 @@ Using 'Dump Node to log' option in variable context menu you also will be able t
47
53
### pgsql_hacker_helper.json
48
54
49
55
This is a configuration file for extension.
50
-
It stored inside `.vscode` directory in your repository -`.vscode/pgsql_hacker_helper.json`.
51
-
You can use config file to extend built-in capabilities if there is no
52
-
support for something yet.
56
+
It stored inside `.vscode` directory in your repository -
57
+
`.vscode/pgsql_hacker_helper.json`. You can use config file to extend built-in
58
+
capabilities if there is no support for something yet.
53
59
54
60
Example json:
55
61
@@ -94,22 +100,57 @@ For more info check [configuration file documentation](./docs/config_file.md).
94
100
95
101
There are 2 settings:
96
102
97
-
- Log level - set minimum level of log messages in Output channel. By default - `INFO`
98
-
- Files with NodeTag files - list of paths points to files that contain NodeTags. By default - `src/include/nodes/nodes.h`, `src/include/nodes/nodetags.h`
103
+
- Log level - set minimum level of log messages in Output channel.
104
+
By default - `INFO`
105
+
- Files with NodeTag files - list of paths points to files that contain NodeTags.
106
+
By default - `src/include/nodes/nodes.h`, `src/include/nodes/nodetags.h`
107
+
108
+
## Compatibility
109
+
110
+
Extension tries to be compatible with multiple versions of both VS Code and
111
+
PostgreSQL.
112
+
113
+
Minimal supported version of:
114
+
115
+
-`VS Code` - 1.30
116
+
-`PostgreSQL` - 8.0
117
+
118
+
> It is tested manually and not all use cases might be covered. If you found
119
+
> bug specific to some version please [create issue](https://github.com/ashenBlade/postgres-dev-helper/issues).
120
+
121
+
Also, extension will target latest VS Code version and try to use the full
122
+
functionality of new versions. So, use latest VS Code versions to get new
123
+
features earlier.
99
124
100
125
## Known Issues
101
126
102
127
Known issues:
103
128
104
129
- Only tested on gdb debugger, UB for other debuggers (i.e. lldb)
105
-
- If in pointer variable was garbage, extension will not detect it and expand this variable (may be garbage)
106
-
- To get NodeTags extension reads all available NodeTag files (from settings), but
107
-
these files may be not created (./configure or make not run). I assume by time
108
-
of debugging start files will be created, so extension catch them and process.
109
-
- Tested only with [ms-vscode.cpptools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) extension
130
+
- If in pointer variable was garbage, extension will not detect it and expand
131
+
this variable (may be garbage)
132
+
- To get NodeTags extension reads all available NodeTag files (from settings),
133
+
but these files may be not created (./configure or make not run). I assume by
134
+
time of debugging start files will be created, so extension catch them and
135
+
process.
136
+
- Tested only with [ms-vscode.cpptools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools)
137
+
extension
110
138
111
139
## Release Notes
112
140
141
+
### 1.2.0
142
+
143
+
Expand range of supported versions both for PostgreSQL (from 8.0) and VS Code
144
+
(from 1.30).
145
+
146
+
Add support for Bitmapset for versions below 16.
147
+
148
+
Add support for List with Linked List implementation.
149
+
150
+
Fix log level updated only after extension or VS Code reload.
151
+
152
+
Fix invalid Node cast in some cases when declared type has `struct` keyword.
153
+
113
154
### 1.1.2
114
155
115
156
Fix invalid `List` behaviour with different declared type - members shown for
0 commit comments