Why is this field deprecated and not published? It really complicates dual maintenance of apps with database fields.
Mailing lists / fpc-devel / 2019-07
TFIeld.lookup problem
6 messages · 2 people ·
- Marco van de Voort 3
- Michael Van Canneyt 3
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Marco van de Voort wroteWhy is this field deprecated and not published? It really complicates dual maintenance of apps with database fields.
Because it is redundant. The fieldkind property is what you need. Set fieldKind=fkLookup
Michael.
Op 2019-07-20 om 14:40 schreef Michael Van Canneyt:
Show quoted text 7 lines
> Why is this field deprecated and not published? It really complicates
> dual maintenance of apps with database fields.
Because it is redundant. The fieldkind property is what you need. Set
fieldKind=fkLookup
As said, it causes annoying problems with dual maintenance of forms for no particular reason (since the property is still there, public). Is it so hard to make it published (stored false if need be?).
Marco van de Voort wrote 12 lines
Op 2019-07-20 om 14:40 schreef Michael Van Canneyt:
>
>> Why is this field deprecated and not published? It really complicates
>> dual maintenance of apps with database fields.
>
> Because it is redundant. The fieldkind property is what you need. Set
> fieldKind=fkLookup
>
As said, it causes annoying problems with dual maintenance of forms for
no particular reason (since the property is still there, public).
Is it so hard to make it published (stored false if need be?).
No, it is not.
But dual maintenance was never a target. Easy porting, yes.
Michael.
Op 2019-07-20 om 16:04 schreef Michael Van Canneyt:
Show quoted text 11 lines
>>> Why is this field deprecated and not published? It really
>>> complicates dual maintenance of apps with database fields.
>>
>> Because it is redundant. The fieldkind property is what you need.
>> Set fieldKind=fkLookup
>>
> As said, it causes annoying problems with dual maintenance of forms
> for no particular reason (since the property is still there, public).
> Is it so hard to make it published (stored false if need be?).
(that came out a bit more whiny then I meant it :-)
No, it is not. But dual maintenance was never a target.
Deliberately frustrating it can't be the object either.
Easy porting, yes.
It makes it unnecessary hard for e.g. example code for shared component packages. So can we please change it? Just say the word, and I'll do it.
Marco van de Voort wrote 20 lines
Op 2019-07-20 om 16:04 schreef Michael Van Canneyt:
>
>>>> Why is this field deprecated and not published? It really
>>>> complicates dual maintenance of apps with database fields.
>>>
>>> Because it is redundant. The fieldkind property is what you need.
>>> Set fieldKind=fkLookup
>>>
>> As said, it causes annoying problems with dual maintenance of forms
>> for no particular reason (since the property is still there, public).
>> Is it so hard to make it published (stored false if need be?).
>
(that came out a bit more whiny then I meant it :-)
> No, it is not.
>
> But dual maintenance was never a target.
Deliberately frustrating it can't be the object either.
That was not the intent.
Show quoted text 5 lines
> Easy porting, yes.
>
It makes it unnecessary hard for e.g. example code for shared component
packages. So can we please change it? Just say the word, and I'll do it.
Sure, go ahead.
Michael.