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 had NULL fields in all records.
>>
>> 3. When limiting the UPDATE to a specific record rather than the entire
>> table and even then setting RDB$Procedure_Source = NULL only when there
>> is some source code to null, then it works fine.
> 
> Only changes from non-NULL to NULL are allowed while updating. You need
> to filter out records already without sources.

Out of curiosity: why? Why not just allow any updates to NULL, even if 
the existing value already is NULL?

Mark
-- 
Mark Rotteveel
  • [firebird-s... Chuck Belanger phytot...@lanset.com [firebird-support]
    • Re: [f... Chuck Belanger phytot...@lanset.com [firebird-support]
      • Re... Helen Borrie hele...@iinet.net.au [firebird-support]
        • ... Chuck Belanger phytot...@lanset.com [firebird-support]
          • ... Dmitry Yemanov dim...@users.sourceforge.net [firebird-support]
            • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
              • ... Dmitry Yemanov dim...@users.sourceforge.net [firebird-support]
    • Re: [f... Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
    • Re: [f... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
      • Re... blackfalconsoftw...@outlook.com [firebird-support]
        • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
    • Re: [f... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
      • Re... blackfalconsoftw...@outlook.com [firebird-support]

Reply via email to