Commit graph

15 commits

Author SHA1 Message Date
Lance Edgar 6e50ea58a8 Fix how we select changes from CORE DB in datasync
to placate SQLAlchemy warnings
2023-06-10 22:13:42 -05:00
Lance Edgar 82892be096 More refactoring, Query.get() => Session.get() 2023-02-12 09:37:31 -06:00
Lance Edgar 0b5930a511 Refactor Query.get() => Session.get() per SQLAlchemy 1.4 2023-02-11 22:06:43 -06:00
Lance Edgar 74b9ec5e1e Avoid deprecated base class, per upstream changes 2021-12-30 15:53:59 -06:00
Lance Edgar a32753a04a Let CORE-POS datasync watcher use alternate "changes" table name
i needed this for sake of online demo, so that 2 separate rattail apps could
both watch the same CORE DB simultaneously
2020-07-09 17:01:23 -05:00
Lance Edgar 8917316a21 Add 2-way sync for basic Member data, CORE <-> Rattail 2020-03-18 11:30:18 -05:00
Lance Edgar 9dbdb81f07 Add 2-way sync for customer contact data, for CORE API <-> Rattail 2020-03-17 18:52:08 -05:00
Lance Edgar cb63644c7d Add support for Rattail -> CORE export/sync for Member data
also refactor CORE -> Rattail logic to use `api.set_member()` etc.
2020-03-17 16:29:35 -05:00
Lance Edgar cd93d3e36b Add support for Department, Subdepartment, Product in Rattail -> CORE API 2020-03-15 15:54:15 -05:00
Lance Edgar af1e38aa18 Oerhaul the Vendor import/export between Rattail and CORE
also, add new DB schema specific to this integration, to hold PKs etc.
2020-03-04 19:05:55 -06:00
Lance Edgar f9071ac6e9 Remove DB-related things from the Rattail -> CORE datasync consumer
since that should only use API, going forward
2020-03-04 13:29:47 -06:00
Lance Edgar 0298e63384 Add initial Rattail -> CORE-POS export logic
only allows "update" for Vendor model so far.  more to come after testing...
2020-03-03 21:45:11 -06:00
Lance Edgar 6f03461114 Add datasync watcher for trigger-populated "changes" table in CORE 2020-03-01 20:00:45 -06:00
Lance Edgar 2a37bb5a49 Cleanup attribute names for CORE Department model 2019-07-23 19:44:32 -05:00
Lance Edgar 810d4726c3 Initial commit 2018-06-01 15:14:49 -05:00