<part host="d51A5A0AE.access.telenet.be" login="n=Mephisto" nick="Mephisto" reason="" time="00:46:33.165+01:00"/>
<join host="dsl-209-90-140-232.tor.primus.ca" login="n=Snak" nick="polvo" time="02:51:34.212+01:00"/>
<join host="d51A5A0AE.access.telenet.be" login="n=Mephisto" nick="Mephisto" time="03:43:35.131+01:00"/>
<join host="189.78.251.23" login="n=no" nick="laubstein" time="03:58:11.181+01:00"/>
<join host="c-71-236-161-195.hsd1.or.comcast.net" login="n=brian" nick="ryerpatch" time="04:14:41.726+01:00"/>
<part host="189.78.251.23" login="n=no" nick="laubstein" reason="Read error: 110 (Connection timed out)" time="04:56:35.661+01:00"/>
<part host="c-71-236-161-195.hsd1.or.comcast.net" login="n=brian" nick="ryerpatch" reason="" time="07:10:02.004+01:00"/>
<join host="81-208-83-237.fastres.net" login="n=[giulio]" nick="[giulio]" time="08:12:19.381+01:00"/>
<join host="62.232.6.162" login="n=XIRCProx" nick="perig" time="08:12:40.139+01:00"/>
<part host="ua-83-227-136-141.cust.bredbandsbolaget.se" login="n=ljo" nick="ljo" reason="Remote closed the connection" time="08:26:12.142+01:00"/>
<join host="sve157.svenska.gu.se" login="n=ljo" nick="ljo" time="08:47:25.031+01:00"/>
<join host="p5B20EE25.dip.t-dialin.net" login="n=wolf" nick="wolf77" time="09:24:58.031+01:00"/>
<part host="81-208-83-237.fastres.net" login="n=[giulio]" nick="[giulio]" reason="Read error: 104 (Connection reset by peer)" time="09:51:21.922+01:00"/>
<message nick="ljo" time="10:04:35.309+01:00">.</message>
<join host="81-208-83-237.fastres.net" login="n=[giulio]" nick="[giulio]" time="10:25:42.14+01:00"/>
<join host="nemi.cs.umu.se" login="i=danielh" nick="danielh" time="10:27:53.929+01:00"/>
<message nick="danielh" time="10:38:52.383+01:00">Hi! I'm having a stupid question that I haven't managed to find the answer to: Can you somehow query for objects that was added to the database since a certain point-in-time? </message>
<message nick="danielh" time="10:39:21.212+01:00">Using some kind of meta-data? (And thus not being forced to specify the added data in the record)</message>
<message nick="ljo" time="10:40:50.413+01:00">To make it portable i would still add the data to the documents.</message>
<message nick="danielh" time="10:42:35.076+01:00">Sadly I'm not in control of what data goes into the documents.. so I'm not sure its possible</message>
<message nick="danielh" time="10:43:51.63+01:00">I'm trying to fetch records from a running database periodically</message>
<message nick="danielh" time="10:44:07.521+01:00">So the hard part is determining what records are new since the last read</message>
<message nick="ljo" time="10:44:19.978+01:00">Maybe you can keep a separate doc for this ctime andor mtime then.</message>
<message nick="danielh" time="10:44:25.956+01:00">...without adding any data to the records</message>
<message nick="danielh" time="10:44:49.749+01:00">possibly</message>
<message nick="danielh" time="10:45:26.148+01:00">but I suppose the database itself does not order the elements in any way usable? Such as an increasing index or something?</message>
<message nick="ljo" time="10:47:13.934+01:00">document order only</message>
<message nick="ljo" time="10:50:40.565+01:00">What is your use case? It is a bit vague for me.</message>
<message nick="perig" time="11:10:52.221+01:00">when stored in eXist, documents are called "resources". From there, we offer some (eXist-specific) functions that can retrieve date-time based information about them ;-)</message>
<message nick="danielh" time="13:11:25.725+01:00">hrm, well back from a meeting (about this subject, actually)</message>
<message nick="danielh" time="13:11:38.853+01:00">And it seems we could work a ctime in there somewhere</message>
<message nick="danielh" time="13:11:47.454+01:00">So then the problem will be solved</message>
<message nick="danielh" time="13:11:55.696+01:00">thanks for your input guys!</message>
<message nick="danielh" time="13:11:58.77+01:00">tata</message>
<join host="dsl-209-90-140-232.tor.primus.ca" login="n=Snak" nick="polvo" time="14:17:55.914+01:00"/>
<part host="d51A5A0AE.access.telenet.be" login="n=Mephisto" nick="Mephisto" reason="Nick collision from services." time="15:27:14.933+01:00"/>
<join host="d51A5A0AE.access.telenet.be" login="n=Mephisto" nick="Mephy" time="15:27:32.967+01:00"/>
<join host="c-71-236-161-195.hsd1.or.comcast.net" login="n=brian" nick="ryerpatch" time="15:30:28.085+01:00"/>
<part host="62.232.6.162" login="n=XIRCProx" nick="perig" time="17:01:17.145+01:00"/>
<part host="81-208-83-237.fastres.net" login="n=[giulio]" nick="[giulio]" reason="Read error: 104 (Connection reset by peer)" time="17:02:03.137+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" time="17:41:32.375+01:00"/>
<join host="81.196.83.67" login="n=thor" nick="rebelThor" time="17:58:14.596+01:00"/>
<message nick="perig" time="18:11:40.22+01:00">.</message>
<message nick="rebelThor" time="18:11:55.862+01:00"> .|</message>
<message nick="wolf77" time="18:31:29.495+01:00">mmmh, why do we get spam on the commits list?</message>
<message nick="perig" time="18:31:58.966+01:00">I think it comes from gmane</message>
<message nick="wolf77" time="18:32:54.771+01:00">possible. but we don't get spam on exist-open, so why on exist-commits?</message>
<message nick="wolf77" time="18:33:10.312+01:00">maybe I missed some setting ...</message>
<part host="81.196.83.67" login="n=thor" nick="rebelThor" reason="Read error: 104 (Connection reset by peer)" time="18:44:05.212+01:00"/>
<message nick="wolf77" time="18:53:47.393+01:00">ok, I think I found it</message>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig_" time="20:11:13.693+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 104 (Connection reset by peer)" time="20:11:14.254+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig_" time="20:36:11.417+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 104 (Connection reset by peer)" time="20:36:11.808+01:00"/>
<part host="sve157.svenska.gu.se" login="n=ljo" nick="ljo" reason="Remote closed the connection" time="20:36:44.792+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 104 (Connection reset by peer)" time="20:51:24.948+01:00"/>
<join host="ua-83-227-136-141.cust.bredbandsbolaget.se" login="n=ljo" nick="ljo" time="21:12:58.995+01:00"/>
<join host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" time="21:18:19.2+01:00"/>
<part host="vil35-2-82-236-174-106.fbx.proxad.net" login="n=perig" nick="perig" reason="Read error: 104 (Connection reset by peer)" time="22:15:58.899+01:00"/>
<part host="p5B20EE25.dip.t-dialin.net" login="n=wolf" nick="wolf77" time="23:04:56.008+01:00"/>
</xlog>