Thank you. I like your suggested bypass because since I posted this problem I've been surrounding the code with begin/end for other reasons. My own bypass had been to use direct assignment: x := (extend TABLE_DEE <etc.>) union x;
Hugh
Search found 121 matches
- Sun Sep 22, 2019 2:11 pm
- Forum: Report a Bug
- Topic: Spurious sytax error with INSERT
- Replies: 3
- Views: 10426
- Mon Sep 09, 2019 5:02 pm
- Forum: Report a Bug
- Topic: insert sometimes doesn't insert anything
- Replies: 1
- Views: 4830
insert sometimes doesn't insert anything
This might have to be just a heads up to begin with. I can't give a specific example at this time because the examples where this bug is hitting me are too complex. Sometimes, when I give an INSERT command, with a complex expression as source and a target of existing high cardinality, the operation ...
- Mon Sep 09, 2019 4:53 pm
- Forum: Report a Bug
- Topic: Spurious sytax error with INSERT
- Replies: 3
- Views: 10426
Spurious sytax error with INSERT
Try this: var x base relation{z char} key{z}; insert x extend TABLE_DEE : {z := '//'}; I get ERROR: Encountered "insert" at line 1, column 1. Was expecting one of: "BEGIN" ... "TCLOSE" ... <TUPLE> ... "WITH" ... <TUPLE> ... I have used a bypass of this kind sometimes: x := (extend TABLE_DEE : {z := ...
- Tue Jan 29, 2019 3:29 pm
- Forum: Report a Bug
- Topic: RENAME in V3.013 incompatible with previous versions
- Replies: 2
- Views: 6075
Re: RENAME in V3.013 incompatible with previous versions
Thanks for the confirmation.
I fully agree with the change. On reflection, I feel rather ashamed of exploiting what I would regard as a bug in previous versions!
Hugh
I fully agree with the change. On reflection, I feel rather ashamed of exploiting what I would regard as a bug in previous versions!
Hugh
- Thu Jan 24, 2019 2:43 pm
- Forum: Report a Bug
- Topic: RENAME in V3.013 incompatible with previous versions
- Replies: 2
- Views: 6075
RENAME in V3.013 incompatible with previous versions
This might not be a bug, but rather a change resulting from a bug fix, but I'm asking the question under this rubric for want of a more appropriate one. In all versions up to V3.012 the following expression was legal: rel{tup{x1 1}} rename {suffix '1' as '', x as y} resulting in rel{tup{y 1}} In V3....
- Tue Nov 27, 2018 2:37 pm
- Forum: Report a Bug
- Topic: WITH not available in a WHERE condition
- Replies: 4
- Views: 10150
Re: WITH not available in a WHERE condition
Yes, I did later think of using parens, but our grammar does specify WHERE <bool exp>.
Hugh
Hugh
- Mon Nov 19, 2018 4:56 pm
- Forum: Report a Bug
- Topic: WITH not available in a WHERE condition
- Replies: 4
- Views: 10150
WITH not available in a WHERE condition
Rel allows the use of WITH in a <bool exp> but not when the <bool exp> is given as a WHERE condition.
I tested this with and .
Hugh
I tested this with
Code: Select all
WITH (x := TRUE) : x
Code: Select all
r WHERE WITH (x := TRUE) : x
Hugh
- Mon Nov 19, 2018 4:50 pm
- Forum: Rel's "DBrowser": The Rel Graphical User Interface
- Topic: Scroll bar disappears in Rel mode
- Replies: 7
- Views: 17537
Re: Scroll bar disappears in Rel mode
Actually I don't have that setting. And now I notice that the problem arises only when I use Edit, and it stays in effect when I cease editing and just use Show.
Hugh
Hugh
- Thu Nov 15, 2018 5:27 pm
- Forum: Rel's "DBrowser": The Rel Graphical User Interface
- Topic: Scroll bar disappears in Rel mode
- Replies: 7
- Views: 17537
Re: Scroll bar disappears in Rel mode
The one on the right.
Hugh
Hugh
- Tue Nov 13, 2018 5:49 pm
- Forum: Rel's "DBrowser": The Rel Graphical User Interface
- Topic: Scroll bar disappears in Rel mode
- Replies: 7
- Views: 17537
Scroll bar disappears in Rel mode
In "Rel" mode, to keep the scroll bar available I have to keep the window very wide, usually with a large amount of unused space, occupying most of my screen. This is annoying when I need to look at that window at the same time as other windows.
The same problem does not arise in command mode.
Hugh
The same problem does not arise in command mode.
Hugh
- Sat Mar 24, 2018 12:01 pm
- Forum: Report a Bug
- Topic: Old database treated as a new one
- Replies: 1
- Views: 4129
Old database treated as a new one
Every time I open a certain database that I've had for several years, I get the "Welcome" thing in Rel and no history in command line mode. I found that the system's history relvar didn't exist, so I created it, using text from another database's backup file, but that didn't help. How can I stop thi...
- Thu Feb 08, 2018 5:07 pm
- Forum: Report a Bug
- Topic: Copied text stays in clipboard when it shouldn't
- Replies: 1
- Views: 3986
Copied text stays in clipboard when it shouldn't
Here's a strange one that has only emerged with improved copy-and-paste in v3.011. I copy something from Rel 's output pane and paste it somewhere, no problem. Then, with Rel still running I go to another (non- Rel )window and use ctrl+c or edit/copy from there. When I then try to paste that somewhe...
- Thu Feb 08, 2018 1:02 pm
- Forum: Report a Bug
- Topic: Column heads for RVAs not treated right when names only selected
- Replies: 3
- Views: 5987
Re: Column heads for RVAs not treated right when names only selected
I've installed v3.011 since I reported this bug and the related one concerning TUPLE{...}. The TUPLE bug seems to have been fixed, but not this one. Here's the example you asked for:
Hugh
Hugh
- Thu Feb 08, 2018 12:54 pm
- Forum: Report a Bug
- Topic: Incorrect display of a tuple with RVAs
- Replies: 4
- Views: 6188
Re: Incorrect display of a tuple with RVAs
Now I find I can't recreate the problem either. Sorry.
Hugh
Hugh
- Thu Feb 08, 2018 12:43 pm
- Forum: Report a Bug
- Topic: Incorrect display of a tuple with RVAs
- Replies: 4
- Views: 6188
Re: Incorrect display of a tuple with RVAs
Please ignore previous post. I didn't read carefully enough.
Hugh
Hugh