applauseoss / djangoevents Goto Github PK

When creating modules, I want to manage one avro folder per module, but the configuration does not allow this.

Hi guys,

I released a new major version of the eventsourcing library. https://pypi.python.org/pypi/eventsourcing/2.1.1

It's not backwards-compatible with the 1.x.x, there are some significant changes. If you wanted to update djangoevents to use the new version, you would need to make a few changes. Would be very happy to help you work through them, if you wanted some help with it.

Hope all's well,

John

should be:
https://github.com/johnbywater/eventsourcing/blob/26c2b41a5c5bc1c754cdc809bb40e1dce175d144/eventsourcing/infrastructure/stored_event_repos/with_sqlalchemy.py#L137
right now:
https://github.com/ApplauseOSS/djangoevents/blob/devel/djangoevents/repository.py#L76

the reason behind is if multiple events get persist to the database, the order of inserts may not be the order of event creation.

Currently we are using publish name for storing events as it is used directly from eventsourcing library. This might be misleading however - it's actually storing an event. We should call it simply store_event instead.

Not sure if we want to keep old method. djangoevents is not mature yet so we can change API without deprecating it first. OTOH, we might want to inform all users by issuing deprecationwarning (https://docs.python.org/3/library/warnings.html#default-warning-filters).

Consider changing the naming of one of app.py and apps.py because right now it's confusing what they do and why we need both.

Currently we have hardcoded event_journal name for the table (https://github.com/ApplauseOSS/djangoevents/blob/devel/djangoevents/models.py#L19). As not default value might be surprising for library users. Let's use default name (djangoevents_event) but allow to configure this.

Tasks

• Create djangoevents.config module which should read DJANGOEVENTS_CONFIG variable from settings.py
• Have a default djangoevents_event for table name
• Use table name from configuration at the model's Meta
• Use table name from configuration at the migration
• Document this at the readme
• Updated changelog and let users know of potentially breaking change (they would need to manually rename table or set table name to event_journal

Hi,

I am very interested in doing event sourcing with django.
It is not easy to understand how to use this library in a new or existing django project.
Also, how easy is it to use it with other django apps in parallel ?

Could you please provide an example project using this module in parallel with django.contrib.auth ?

Does an open source project on github or elsewhere using this module exist that we could refer to ?

Many thanks.
M0dM