It must be a duck, cause calling this standard behavior is quackers. There
are many issues with object fields. I for one refuse to use them (Yes I
know how powerful they are and can be) as I do so much with sql and can not
get them using a sql statement.  I have commented before that 4D should not
implement a ew data type for a field unless they also update sql in some
way to accommodate it.

It would or examples be strange it they added a pony type fields like SQL
already has and did not support the same.

In fact there UUID implementation is strange as well. How do you tell if
the field is a UUID - type = alpha and length = 0, when you get field
properties

Regards

Chuck

On Tue, Oct 31, 2017 at 4:09 PM, David Adams via 4D_Tech <
[email protected]> wrote:

> > It looks like this bug ACI0097454 was marked as Standard Behavior on
> October 24th.
>
> Smells like a bug.
> Looks like a bug.
> Sounds like a bug.
> Walks like a bug.
>
> I mean, if you have a light switch that gives you a shock every time you
> touch it, you wouldn't say "Oh, it always does that. It's standard
> behavior." I mean, that's an accurate description (ouch!), but it's not a
> reasonable reaction.
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:[email protected]
> **********************************************************************
>



-- 
-----------------------------------------------------------------------------------------
 Chuck Miller Voice: (617) 739-0306 Fax: (617) 232-1064
 Informed Solutions, Inc.
 Brookline, MA 02446 USA Registered 4D Developer
       Providers of 4D, Sybase & SQL Server connectivity
          http://www.informed-solutions.com
-----------------------------------------------------------------------------------------
This message and any attached documents contain information which may be
confidential, subject to privilege or exempt from disclosure under
applicable law.  These materials are intended only for the use of the
intended recipient. If you are not the intended recipient of this
transmission, you are hereby notified that any distribution, disclosure,
printing, copying, storage, modification or the taking of any action in
reliance upon this transmission is strictly prohibited.  Delivery of this
message to any person other than the intended recipient shall not
compromise or waive such confidentiality, privilege or exemption
from disclosure as to this communication.
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to