RE: [personal kdb+] kdb+tick with schemaless events

Community Support
,
1

User-Agent: Workspace Webmail 5.14.0Message-Id: <20150428203053.85f80dae80d1d2f2e266ec6278e6cbe8.49e401c4f0.wbe@email07.europe.secureserver.net>From: “David Demner (AquaQ)” <david.demner>To: personal-kdbplus@googlegroups.comSubject: RE: [personal kdb+] kdb+tick with schemaless eventsDate: Tue, 28 Apr 2015 20:30:53 -0700Mime-Version: 1.0


q)t:([]time:3?0D; sym:til 3; data:3#enlist(1 2!(1 2;1 2)))
q)`:t/ set 0#t
q)`:t/ upsert t
q)value`:t/
time sym data
--------------------------------------
0D09:25:33.805802464 0 1 2!(1 2;1 2)
0D12:24:36.672738790 1 1 2!(1 2;1 2)
0D12:23:00.641756951 2 1 2!(1 2;1 2)


kdb+ does this to protect you from yourself when you're trying to write down complex columns that can't be efficiently accessed.

2

Awesome. I never would have guessed that.For anyone else interested: .Q.hdpf works fine with complex columns, no modification necessary. The p# attribute still works on the sym column, so queries for a specific event type should still be fast. 29.04.2015, 08:47, "David Demner (AquaQ)" <david.demner>:&gt; q)t:([]time:3?0D; sym:til 3; data:3#enlist(1 2!(1 2;1 2)))&gt; q):t/ set 0#t> q):t/ upsert t&gt; q)value:t/> time ? ? ? ? ? ? ? ? sym data> --------------------------------------> 0D09:25:33.805802464 0 ? 1 2!(1 2;1 2)> 0D12:24:36.672738790 1 ? 1 2!(1 2;1 2)> 0D12:23:00.641756951 2 ? 1 2!(1 2;1 2)>> kdb+ does this to protect you from yourself when you’re trying to write down complex columns that can’t be efficiently accessed.>>> </david.demner>