When importing dump from 3.5 into 4.0, metadata's @last-modified is set to "now"

19 views
Skip to first unread message

Bruno Lopes

unread,
Jan 15, 2018, 12:11:57 PM1/15/18
to RavenDB - 2nd generation document database
Pretty much what it says on the subject.

I would expect the @last-modified field to be preserved across export/imports. Does that make sense?

I noticed this on the revisions, which end up all labeled with the import data on the UI.

Oren Eini (Ayende Rahien)

unread,
Jan 15, 2018, 12:35:39 PM1/15/18
to ravendb
That is actually how it works in 3.x now. However, that is indeed an issue, we'll fix ti

Hibernating Rhinos Ltd  

Oren Eini l CEO Mobile: + 972-52-548-6969

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

 


--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Oren Eini (Ayende Rahien)

unread,
Jan 15, 2018, 12:36:13 PM1/15/18
to ravendb

Bruno Lopes

unread,
Jan 15, 2018, 12:48:15 PM1/15/18
to RavenDB - 2nd generation document database
Thanks.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages