You are very welcome, Alastair!
As always, the pleasure is all mine.
There is so much being implemented that for some reason, if you
missed the Tip of the Day, or forgot to refer to What's New PDF, it
can create some confusion or sudden surprises. Thus, my reason to
step-in immediately, before someone makes their own assumptions,
etc., and creates confusion for the rest of the users on this list.
Yes, personally, I do monitor this list with interest, and always do
my best to reply, help, and/or clarify as much as I can while keeping
up with my 16-18 hours a day, every day, of R:BASE development jobs
and responsibilities.
For your information, the COLCHECK setting was first introduced on
August 28, 2015 and then officially released on September 24, 2015
(Versions 9.5 and 10.0).
Here is a snippet from the original Tip of the Day, posted on August 28, 2015.
Please feel free to reach out to me if you have further questions.
Hope that helps!
Very Best R:egards,
Razzak
-----------------------------------------------------------------------
Friday, August 28, 2015
Tip of the Day: About the New COLCHECK Setting
Product.: R:BASE eXtreme 9.5 (32/64) and R:BASE X (Version 10)
Build...: 9.5.5.20924, 10.0.1.10924 or higher
Section.: Settings
Keywords: COLCHECK, CREATE VIEW, CREATE TEMPORARY VIEW, AS alias
Did you know that the upcoming update of R:BASE eXtreme 9.5 (32/64)
and the official release of R:BASE X (Version 10), to be released on
September 24, 2015, include a new COLCHECK setting?
The additional COLCHECK setting has been introduced to manage common
column names and corresponding data types when used as ALIAS names
while defining a new VIEW or modifying an existing VIEW.
COLCHECK specifies if columns will be checked for consistency when
making views. When COLCHECK is ON (the default), view alias/column
names will be checked for consistency to other occurrences of those
names in the database, when the view is created.
Syntax:
SET COLCHECK ON/OFF
Similar checking is already in place when creating or modifying
tables, and when attaching tables to a database, where R:BASE
requires an alias that does not cause name/data type conflicts.
If an application requires COLCHECK be off to define a view, the
proper results should not be expected once COLCHECK is switched back
to ON when using the view. If a view needs to be created with
COLCHECK OFF, it also needs to be used with COLCHECK OFF.
An impact may occur for a view that has already been defined, because
when COLCHECK is ON, the values generated for the view will follow
the data type of the alias. If an error occurs, the view definition
should be reviewed.
-----------------------------------------------------------------------
At 12:51 PM 1/27/2017, Alastair Burr wrote:
Thank you very much, Razzak, setting ColCheck off did the trick.
I notice that if I turn ColCheck back on I immediately get the error
message again as soon as I try to use the view.
I have looked at the names in the view almost endlessly today to try
and see where the error was so I am puzzled as to where R:Base finds
a difference.
I think I would rather correct that than run with ColCheck set off
all the time. Obviously I can change the setting in a command file
before and after use but what has raised this problem is the error
message is received whenever I reconstruct the database from
unloads. (But not with Reload.)
This may be a complete misinterpretation but I also have a suspicion
that this particular error has been causing problems with my user
privileges. Is that possible? If so, I may have to run with ColCheck
set to off all the time. With that in mind when was ColCheck
introduced and/or was it changed with the upgrade to v10?
Again thanks,
Regards,
Alastair.
On 27/01/2017 16:38, A. Razzak Memon wrote:
Alastair,
A few questions ...
01. What is the COLCHECK setting?
SHOW COLCHECK
02. What results do you get when turning OFF the COLCHECK setting.
SET COLCHECK OFF
FYI, COLCHECK ON setting checks the consistency for column names
and data types when making views.
Hope that provides you with some blue's clues ...
Very Best R:egards,
Razzak.
At 11:24 AM 1/27/2017, Alastair Burr wrote:
I know it's Friday but can anybody see what's wrong with this view
(an image so that hopefully the email system doesn't mangle my layout):
If it hasn't, there should be 6 columns so that I could see the
columns and data types (first 5 rows remmed out) more easily.
I am not sure that I am defining the time entries correctly - I've
tried with as well as without quotes.
I am pretty sure I have the data types right - despite the error message.
I am not sure that I have the group by right. I only really need
to group by: T21.Concert_Date, T22.Full_Name, T23.Full_Name (date,
venue name & artist name).
--
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
