01.06.2018 14:49, Mark Rotteveel wrote:
> Out of curiosity: why? Why not just allow any updates to NULL, even if
> the existing value already is NULL?
Setting NULL to NULL means the record wasn't changed. From the engine
POV it's the same as e.g. SET RDB$PROCEDURE_ID = RDB$PROCEDURE_ID, i.e.
On 1-6-2018 11:44, Dmitry Yemanov dim...@users.sourceforge.net
[firebird-support] wrote:
> 01.06.2018 10:30, Chuck Belanger wrote:
>>
>> 2. The difference turned out to be that for one there was actually some
>> source code in the fields. While the other that threw an error message,
>> already
01.06.2018 10:30, Chuck Belanger wrote:
>
> 2. The difference turned out to be that for one there was actually some
> source code in the fields. While the other that threw an error message,
> already had NULL fields in all records.
>
> 3. When limiting the UPDATE to a specific record rather than
On 2018-05-31 23:48, blackfalconsoftw...@outlook.com [firebird-support]
wrote:
> Thanks for the heads up, Mark...
>
> However, Carlos' explanation when I read through it again, does appear
> to be a little confusing at the least.
I have read it again, and I don't see how it is confusing. Might
> Also, apparently, this is not a blanket restriction, since I can
> successfully run the UPDATE RDB$PROCEDURES on at least 1 other
> converted DB (that is essentially the same as the DB I cannot runthis
> UPDATE on).
Smells like a privileges problem. The updater has to be SYSDBA,
Thanks for the heads up, Mark...
However, Carlos' explanation when I read through it again, does appear to be a
little confusing at the least.
Why not simply disallow it altogether and be consistent?
As I just mentioned in another reply to you, no one breaks into databases to
steal
On 2018-05-31 18:14, blackfalconsoftw...@outlook.com [firebird-support]
wrote:
> I just finished a complete review of Carlos' migration guide. I read
> it quite carefully but completely missed what appears to be a
> contradiction in his explanations for the updating of the source-code
> fields
31.05.2018 18:14, blackfalconsoftw...@outlook.com [firebird-support] wrote:
> However, maybe Firebird 3.x.x does NOT allow this as Carlos' manual
> suggests...
I've just trued:
SQL> show version;
Server version:
Firebird/Windows/Intel/i386 (access method), version "WI-V3.0.2.32703 Firebird
Thank you. However, I am not clear at all about how to do this with SQL DDL.
Also, apparently, this is not a blanket restriction, since I can
successfully run the UPDATE RDB$PROCEDURES on at least 1 other converted
DB (that is essentially the same as the DB I cannot run this UPDATE on).
