Search found 49 matches
- Fri Aug 17, 2018 7:35 am
- Forum: Language Issues
- Topic: Fyi using the RANK operator with a rva
- Replies: 3
- Views: 13679
Re: Fyi using the RANK operator with a rva
My mistake. This query, without the projection on GRP.RVA, will cause a fatal error: REL{TUP{KEY. 1,ID "A"}, TUP{KEY. 2,ID "A"}, TUP{KEY. 3,ID "B"}, TUP{KEY. 4,ID "B"}, TUP{KEY. 5,ID "B"}} GROUP{KEY.} AS GRP.RVA EXTEND {RANKS.RVA:=GRP.RVA RANK(ASC KE...
- Fri Aug 17, 2018 4:51 am
- Forum: Language Issues
- Topic: Fyi using the RANK operator with a rva
- Replies: 3
- Views: 13679
Fyi using the RANK operator with a rva
The RANK operator is extremely useful especially when used with rva's (relation valued attributes). But in this context you have to be careful. For example, given this relation: REL{TUP{KEY. 1,ID "A"}, TUP{KEY. 2,ID "A"}, TUP{KEY. 3,ID "B"}, TUP{KEY. 4,ID "B"}...
- Thu Aug 16, 2018 5:54 am
- Forum: Language Issues
- Topic: Editing a rva
- Replies: 1
- Views: 8971
Editing a rva
Editing a rva is working in Rel versions 3.010 and 3.011.
It's not working in version 3.012 although it's possible to create an rva.
It's not working in version 3.012 although it's possible to create an rva.
- Thu Aug 16, 2018 5:45 am
- Forum: Language Issues
- Topic: SEARCH for multiple strings
- Replies: 1
- Views: 9097
SEARCH for multiple strings
MATCHES is using a regex that looks for 2 strings, "40" and "GS". REL{TUP{ID 1,A "5A053"}, TUP{ID 2, A "64GS6"}, TUP{ID 3, A "YYYY"}, TUP{ID 4, A "X40F"}} WHERE MATCHES(A,"(.*40.*)*(.*GS.*)*") It should return a tuple where it fin...
- Thu Aug 16, 2018 4:17 am
- Forum: Discussion
- Topic: FYI on operator SEARCH
- Replies: 1
- Views: 20972
FYI on operator SEARCH
This is a quote about the new SEARCH operator in Rel version 3.012: "new built-in operator SEARCH(t TUPLE{*}, regex CHAR) RETURNS BOOLEAN, which returns true if any CAST_AS_CHAR(a), where a is an attribute of t, matches regex." Your first inclination may be to assume that a is referring to...
- Thu Jul 12, 2018 7:59 am
- Forum: Report a Bug
- Topic: Type Decimal identity crisis
- Replies: 3
- Views: 13679
Re: Type Decimal identity crisis
I understand the need for a aggregate max operator but what I was really trying to get at was that duplicate values are not being recognized and eliminated. WRITELN REL{TUP{D Decimal(7.42,2)}, TUP{D Decimal(7.42,2)}, TUP{D Decimal(7.42,2)}} ; RESULT: RELATION {D Decimal} { TUPLE {D Decimal(7.42, 2)}...
- Sat Jun 30, 2018 8:08 am
- Forum: Report a Bug
- Topic: There's no escape
- Replies: 1
- Views: 10673
There's no escape
The escape character is always decremented by 1 after saving a script in the database and then re-opening it.
Save WRITELN REPLACE_ALL("RANDOM()","ANDOM\\(\\)","") ;
Re-open the script and get:
WRITELN REPLACE_ALL("RANDOM()","ANDOM\(\)","") ;
Save WRITELN REPLACE_ALL("RANDOM()","ANDOM\\(\\)","") ;
Re-open the script and get:
WRITELN REPLACE_ALL("RANDOM()","ANDOM\(\)","") ;
- Sat Jun 30, 2018 8:05 am
- Forum: Report a Bug
- Topic: Type Decimal identity crisis
- Replies: 3
- Views: 13679
Type Decimal identity crisis
VAR TESTD PRIVATE INIT( REL{TUP{ID 1,D Decimal(5.5,2)}, TUP{ID 2,D Decimal(7.0,0)}, TUP{ID 3,D Decimal(7.0,0)}, TUP{ID 4,D Decimal(7.0,0)}, TUP{ID 5,D Decimal(14.5,2)}, TUP{ID 6,D Decimal(23.5,2)}, TUP{ID 7,D Decimal(23.5,2)}, TUP{ID 8,D Decimal(35.5,2)}, TUP{ID 9,D Decimal(42.5,2)}} )KEY{ID}; //SA...
- Mon Apr 09, 2018 8:45 am
- Forum: Report a Bug
- Topic: Problem with ALTER TYPE_OF
- Replies: 5
- Views: 15535
Re: Problem with ALTER TYPE_OF
How stunningly obvious . How stunningly stupid I feel Nevertheless, thanks!
- Mon Apr 09, 2018 12:59 am
- Forum: Report a Bug
- Topic: Problem with ALTER TYPE_OF
- Replies: 5
- Views: 15535
Re: Problem with ALTER TYPE_OF
Hi, Any operator I try with the signature OPERATOR INTEGER(P CHARACTER) RETURNS INTEGER works outside of ALTER VAR. When ALTER VAR is used it always returns an error that the string is invalid: ERROR: RS0390: '"10"' isn't a valid number. Any chance you can spoon feed the appropriate operat...
- Sat Apr 07, 2018 12:40 am
- Forum: Language Issues
- Topic: Option to limit type violation to only the type
- Replies: 1
- Views: 10157
Option to limit type violation to only the type
The following are two user defined type violations that can occur in an operator: ERROR: RS0037: Selector CHECK.FOR.MIXED.NUMERICAL.AND.NON.NUMERICAL.RANGES.WHICH.ARE.INVALID(BOOLEAN) violates POSSREP constraint in type 'FOR.IDS.MULTIPLIERS.AND.STRING.PART.NAMES..NUMERICAL.RANGES.WHERE.BEGINNING.AND...
- Tue Apr 03, 2018 5:34 am
- Forum: Report a Bug
- Topic: Problem with ALTER TYPE_OF
- Replies: 5
- Views: 15535
Re: Problem with ALTER TYPE_OF
Currently I would like new users to have the ability to open a relvar with multiple attributes with type character in Design view and change any of these character based attributes to either integer or rational (via ALTER VAR TYPE_OF) simply using point and click. Being able to change an integer bas...
- Sun Apr 01, 2018 6:26 am
- Forum: Report a Bug
- Topic: Problem with ALTER TYPE_OF
- Replies: 5
- Views: 15535
Problem with ALTER TYPE_OF
I like ALTER especially as a handy point and click convenience. VAR T1 BASE REL{A CHAR, B INT, C RAT, D CHAR, E INT, F RAT}KEY{ }; T1:=REL{TUP{A "10", B 10, C 10.0, D "20", E 20, F 20.0}}; Changes from integer and rational respectively to character are successful. ALTER VAR T1 TY...
- Wed Mar 28, 2018 4:41 am
- Forum: Language Issues
- Topic: Aditional operator functionality
- Replies: 2
- Views: 10309
Re: Aditional operator functionality
Sorry for the long delay in responding.
I should have been clear, I was referring specifically to anonymous operators.
I should have been clear, I was referring specifically to anonymous operators.
- Wed Mar 28, 2018 4:30 am
- Forum: Report a Bug
- Topic: Problem using code to access external data
- Replies: 1
- Views: 22069
Problem using code to access external data
This VAR declaration to access data in sql server 2016 worked as expected in Rel v3.004 but does not work with v3.010 or v3.011: VAR TEST4 EXTERNAL JDBC "jdbc:jtds:sqlserver://localhost:1433;databaseName=JUDYDB1,**,********,TEST1"; It returns the error: ERROR: Encountered "VAR" a...