Newbie question grab bag!

EventStoreDB
#1

Hello all, I debated making separate topics for these but my list kept growing. Thanks for any time/info you can spare!

  • How do you delete entries? I see in the .NET API functions for deleting streams…
  • I think I saw somewhere that events have their own internal timestamp (or maybe it was sequence?) So it it possible to archive events and maintaining their data exactly, or would I need to add some kind of metadata timestamp?
  • I saw in an older talk by Greg Young where he mentions something about result sets having a limited lifetime. In what scenarios are result sets not permanent?
  • What is the EventStore.Rags assembly?
  • How would I go about projecting events elsewhere - say, to a message queue or database?
  • Is the namespace for streams flat? What about for projections?

Again, I appreciate any and all input.

J

#2

For 1, consider update a special case of delete [and vice versa]: http://goodenoughsoftware.net/2013/05/28/why-cant-i-update-an-event/

You can set maxAge/maxCount.

#3
  • You can’t delete entries directly, what use case did you have for that?
  • Each event has a timestamp (you can see this by viewing an Event in the webui), depending on how you were planning to do archiving you could take the full Event data and archive it (this would included the stream it came from, position in that stream, etc.)
  • EventStore.Rags is the configuration changes made in 3.0.0 (more information http://blog.pieterg.com/the-adventures-of-rags/ and https://geteventstore.com/blog/20140905/event-store-3.0.0-new-configuration-options/index.html).
  • If you want to project your data to another source then you would need to set up something that would subscribe to the relavant streams, and then “push” this data out to the relevant source
#4

inline

Hello all, I debated making separate topics for these but my list kept
growing. Thanks for any time/info you can spare!

How do you delete entries? I see in the .NET API functions for deleting
streams...

You can use $maxAge/$maxCount to have older events disappear or you
can use truncate before to delete events prior to event #x. There is a
post linked to on this thread that explains why things are like this.

I think I saw somewhere that events have their own internal timestamp (or
maybe it was sequence?) So it it possible to archive events and maintaining
their data exactly, or would I need to add some kind of metadata timestamp?

They have a sequence and they have a timestamp though you should use
the sequence and not the timestamp for things like archiving

I saw in an older talk by Greg Young where he mentions something about
result sets having a limited lifetime. In what scenarios are result sets
not permanent?

Result sets of what?

What is the EventStore.Rags assembly?

Its argument processing

How would I go about projecting events elsewhere - say, to a message queue
or database?

Well you can use the ES essentially as a queue but you would want a
subscription.

There are 3 kinds of subscriptions.
http://docs.geteventstore.com/introduction/subscriptions/

Is the namespace for streams flat? What about for projections?

As of now it is