Re: ORDA (Why does query fail to find zero uuid value, i.e ("0"*32))

2019-08-13 Thread Kirk Brooks via 4D_Tech
Jeremy,
Try searching the UUID fields for:  "20202020202020202020202020202020"

I got that here:  https://kb.4d.com/assetid=77576

On Tue, Aug 13, 2019 at 3:46 PM Jeremy French via 4D_Tech <
4d_tech@lists.4d.com> wrote:

> Give the following
>
> Table with:
> 1) primary key "key_uuid"
> 2) another field named "some_key_uuid"
> 3) 20-records
> 4) 12 of 20 have value assigned to "some_key_uuid"
> 5) 8 of 20 have no value assigned to "Some_key_uuid". Field value is
> 32-zeroes
>
> Code to locate the 8-records whose "some_key_uuid" contains 32-zeroes:
>
> 
> C_OBJECT($not_assigned1_eso)
> C_OBJECT($not_assigned2_eso)
> C_TEXT($key_t)
>
> $not_assigned1_eso:=ds[Table name(->[test])].query(Field
> name(->[test]some_uuid_key)+" = :1";String(32*"0"))
>
> $key_t:=(32*"0")
> $not_assigned2_eso:=ds.test.query("some_uuid_key = :1";$key_t)
>
> QUERY([test];[test]some_uuid_key=(32*"0"))
> 
>
> Why does ORDA **fail** to locate the entities with 32-zeroes in
> "some_key_uuid", but legacy 4D **does** locate the 8-records?
>
> Here's what I see in the debugger:
>
> https://i.postimg.cc/Pfy88KhZ/p01-orda-vs-legacy-query.png
>
> **
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **



-- 
Kirk Brooks
San Francisco, CA
===

What can be said, can be said clearly,
and what you can’t say, you should shut up about

*Wittgenstein and the Computer *
**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**

ORDA (Why does query fail to find zero uuid value, i.e ("0"*32))

2019-08-13 Thread Jeremy French via 4D_Tech
Give the following

Table with:
1) primary key "key_uuid"
2) another field named "some_key_uuid"
3) 20-records
4) 12 of 20 have value assigned to "some_key_uuid"
5) 8 of 20 have no value assigned to "Some_key_uuid". Field value is 32-zeroes

Code to locate the 8-records whose "some_key_uuid" contains 32-zeroes:


C_OBJECT($not_assigned1_eso)
C_OBJECT($not_assigned2_eso)
C_TEXT($key_t)

$not_assigned1_eso:=ds[Table name(->[test])].query(Field 
name(->[test]some_uuid_key)+" = :1";String(32*"0"))

$key_t:=(32*"0")
$not_assigned2_eso:=ds.test.query("some_uuid_key = :1";$key_t)

QUERY([test];[test]some_uuid_key=(32*"0"))


Why does ORDA **fail** to locate the entities with 32-zeroes in 
"some_key_uuid", but legacy 4D **does** locate the 8-records?

Here's what I see in the debugger:

https://i.postimg.cc/Pfy88KhZ/p01-orda-vs-legacy-query.png

**
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**