Search found 9 matches
- Wed Oct 31, 2012 3:03 am
- Forum: Report a Bug
- Topic: Relclient operator with writeln has no output
- Replies: 1
- Views: 8671
Relclient operator with writeln has no output
I don't know if this is an error or a feature. With this operator defined: operator huh1 ( n integer ) returns relation { i integer }; begin; writeln "Hello"; return relation { tuple { i n }}; end; end operator; Calling the operator from the rel client gives no output: Response response = ...
- Thu Oct 18, 2012 4:40 am
- Forum: Rel Examples
- Topic: A very simple rel client.
- Replies: 1
- Views: 9910
A very simple rel client.
I am starting to write some client code for Rel. Here is code to call a predefined function: package brc; import java.io.IOException; import ca.mb.armchair.rel3.client.Connection; import ca.mb.armchair.rel3.client.Response; import ca.mb.armchair.rel3.client.Value; import ca.mb.armchair.rel3.client.s...
- Wed Nov 16, 2011 3:33 am
- Forum: Report a Bug
- Topic: Insert private relation into relation Serializable Error
- Replies: 1
- Views: 8314
Insert private relation into relation Serializable Error
Running the following in DBrowser gives me this error: ERROR: Table: insert relation failed: java.io.NotSerializableException: ca.mb.armchair.rel3.storage.RelvarPrivateCell var items private relation { id integer, name character } init ( relation { tuple {id 1, name "hi" }, tuple {id 2, na...
- Thu Nov 10, 2011 3:37 am
- Forum: Language Issues
- Topic: How Does One Update a Relation in a Relation
- Replies: 1
- Views: 8636
How Does One Update a Relation in a Relation
It seems like I should be able to do something like this: update x where a = 1 ( update b (c := 33) ); With the following relvar: var x private relation { a integer, b relation { c integer }} init ( relation {tuple {a 1, b relation {tuple {c 2}}}}) key {a}; But I just get an error: "ERROR: Expe...
- Wed Sep 21, 2011 11:57 pm
- Forum: Report a Bug
- Topic: Update not working for private relvar
- Replies: 4
- Views: 11872
Re: Update not working for private relvar
Great.
I look forward to trying out the fix.
I look forward to trying out the fix.
- Wed Jul 06, 2011 3:36 am
- Forum: Report a Bug
- Topic: Serializable Error with Group Relation Assignment
- Replies: 2
- Views: 9699
Serializable Error with Group Relation Assignment
Running the following with DBrowser gives me ERROR: RelDatabase: RelvarPrivate setValue failed: com.sleepycat.util.RuntimeExceptionWrapper: java.io.NotSerializableException: ca.mb.armchair.rel3.storage.RelDatabase var cons real relation { id integer, kind integer, value relation { price integer, qua...
- Mon Jul 04, 2011 5:57 pm
- Forum: Report a Bug
- Topic: Updating relation attribute gives an error
- Replies: 2
- Views: 9376
Updating relation attribute gives an error
var x real relation { a integer, b relation { c integer }} init ( relation {tuple {a 1, b relation {tuple {c 2}}}}) key {a}; var y private relation { c integer } init ( relation { tuple { c 88 }}) key {c}; update x where a = 1 ( b := y ); ------ Executing the above with DBrowser gives error: ca.mb.a...
- Mon Jul 04, 2011 5:50 pm
- Forum: Report a Bug
- Topic: Update not working for private relvar
- Replies: 4
- Views: 11872
Update not working for private relvar
// This works when executed in the DBrowser var ok real relation { a integer, b integer } init (relation {tuple { a 1, b 1 }}) key { a }; update ok where a = 1 ( b := 2 ); // This doesn't var notok private relation { a integer, b integer } init (relation {tuple { a 1, b 1 }}) key { a }; update notok...
- Mon Jul 04, 2011 5:47 pm
- Forum: Report a Bug
- Topic: Comment after last command gives error
- Replies: 1
- Views: 8430
Comment after last command gives error
var a integer ;
// Comments after code cause an error.
---
Executing the above in the DBBrowser results in an error:
ERROR: Encountered "var" at line 1, column 1.
Remove the comment and things are ok.
// Comments after code cause an error.
---
Executing the above in the DBBrowser results in an error:
ERROR: Encountered "var" at line 1, column 1.
Remove the comment and things are ok.