The Rel Forum

I doubt this so much a bug but more likely a limitation: when I declare a virtual relvar with a non-empty <candidate key def list> it doesn't get enforced. Furthermore there's no note of it existing in the catalog either. It would be good to add this to the Limitations section of the web site. Perso...

Cool. We much prefer the new Tutorial D native user-defined types anyway but I just thought I'd mention it since it's shipped as a demo example.

No worries. I was just very confused until I realized because I'm usually very good at remembering passwords, given a few tries.

The old Rel web site had substantial information on Rel's capability to accept user-defined type definitions written in Java, but I can no longer find this information any more. We have a student that wants to use the Date type defined in the provided TypeDate.d script, but an error message appears....

In Rel version 0.3.17 Alpha the provided script files for Windows, DBrowser.bat and Rel.bat, attempt to pass command-line parameters using Unix notation and Rel complains bitterly about it.

No biggie, but it has confused some of our users.

No wonder I can never member my password for this site... The password reset e-mail says: Password: <Randomly assigned password> You can of course change this password yourself via the profile page. But when I go to my profile page I get: General Error SQL ERROR [ postgres ] ERROR: column f.field_sh...

One of our students uncovered the following bug in Rel 0.3.17 Alpha. TYPE DATE POSSREP { c CHAR CONSTRAINT LENGTH ( c ) = 8 AND IS_DIGITS ( c ) }; VAR TEST BASE RELATION {ID INTEGER, D DATE} KEY{ID}; TEST := RELATION {TUPLE {ID 1, D "15061989"}}; The value "15061989" is a charact...

The <substitute> operator does not always parse correctly. Example: UPDATE S (STATUS := 17) The opening parenthesis is interpreted as being part of the expression to perform substitution on rather than the beginning of the assignment. It is taken as denoting the opening parenthesis for a user-define...

Sounds like putting a colon in the filename caused an NTFS Alternate Data Stream to be written to, which is pretty sweet because most applications don't understand them.

Some information: http://www.heysoft.de/nt/ntfs-ads.htm