(let [schema [{:db/ident       :foo/checked?
               :db/valueType   :db.type/boolean
               :db/cardinality :db.cardinality/one}
              {:db/ident       :foo/id
               :db/valueType   :db.type/string
               :db/unique      :db.unique/identity
               :db/cardinality :db.cardinality/one}]
      {:keys [db-after]} (d/with (d/with-db @user/conn) {:tx-data schema})
      {:keys [db-after]} (d/with db-after {:tx-data [{:foo/id       "ok"
                                                      :foo/checked? true}
                                                     {:foo/id "not-ok"}]})]
  {:ok        (d/pull db-after {:eid      [:foo/id "ok"]
                                :selector '[:db/id
                                            (:foo/checked? :default false)]})
   :not-ok    (d/pull db-after {:eid      [:foo/id "not-ok"]
                                :selector '[:db/id
                                            (:foo/checked? :default false)]})
   :not-ok-42 (d/pull db-after {:eid      [:foo/id "not-ok"]
                                :selector '[:db/id
                                            (:foo/checked? :default 42)]})})
=>
{:ok {:db/id 60332402039328370, :foo/checked? true},
 :not-ok {:db/id 65148262968987251, :foo/id "not-ok"},
 :not-ok-42 {:db/id 65148262968987251, :foo/checked? 42}}

what was the expectation with :not-ok-42 @souenzzo?

It's just to confirm that the issue is with false value: once it work with the value 42, everything else inside the test scenario is ok. @ghadi

i think i understand

it's actually a correct test case

but illustrative

@souenzzo @ghadi that looks like a bug to me. I’ve made a case in support and I’ll track it down this weekend.

Thanks!

Is it normal for the client to take longer to start up than the peer for a very small DB ?