alecodes/synchronizator-go
Archived
2
0
Fork 0
generated from alecodes/base-template
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Update Definitions

Alexander Navarro 2024-11-10 19:18:04 +00:00
parent c87443df4a
commit 385e1e252e
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Definitions.md

@ -9,7 +9,7 @@ The idea came after the realization that 2 small projects could share a portion
The purpose of the library is to abstract the common part of synchronization between different platforms that have it's data in different formats or structures. The purpose of the library is to abstract the common part of synchronization between different platforms that have it's data in different formats or structures.
### What is/will be implemented: ## What is/will be implemented:
- [ ] Copy of the external data in a local database - [ ] Copy of the external data in a local database
- [ ] Interfaces for structure definitions and utilization and consumption for integration in external programs - [ ] Interfaces for structure definitions and utilization and consumption for integration in external programs
@ -27,10 +27,10 @@ The purpose of the library is to abstract the common part of synchronization bet
- [ ] Select most weighted in a partial match - [ ] Select most weighted in a partial match
- [ ] Ignore - [ ] Ignore
### What won't be implemented ## What won't be implemented
### Tech Stack and Misc ## Tech Stack and Misc
- Use a graph database since we are mostly interested in the relation between items - Use a graph database since we are mostly interested in the relation between items
- TBD which one, but since is intended to be used in small programs, sqlite and postgres should suffice with their recursive CTE statements and go handles them natively - TBD which one, but since is intended to be used in small programs, sqlite and postgres should suffice with their recursive CTE statements and go handles them natively