Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

store data in memory structures instead of XML #124

Closed
h1alexbel opened this issue Aug 28, 2024 · 3 comments · Fixed by #125
Closed

store data in memory structures instead of XML #124

h1alexbel opened this issue Aug 28, 2024 · 3 comments · Fixed by #125
Assignees
@h1alexbel
Labels
enhancement New feature or request

Comments

@h1alexbel
Copy link
Owner

h1alexbel commented Aug 28, 2024 •
edited
Loading

@h1alexbel I have a general question. Why we need sql database? I think if we're choosing in memory solution we can use just some list(or any other collection) of data structs. IMHO it would be much simpler then have some sql storage. No requests needed. Need to add/remove something – just call github#add_user/github#add_repo and etc. If we need some history of changes we can build some state machine that will track all changes that was made by user and it would build report based on it's history

@l3r8yJ I thought about that. We can create some data structures in memory and operate with them. In the end we should obtain a hierarchy of these structures.

Originally posted by @h1alexbel in #123 (comment)
@h1alexbel h1alexbel added the enhancement New feature or request label Aug 28, 2024
@h1alexbel h1alexbel self-assigned this Aug 28, 2024
@github-actions GitHub Actions
Copy link

@h1alexbel
Main quality problem: Lack of clear bug description.
Suggestion: Rephrase as a specific, actionable bug report with steps to reproduce and expected behavior.

h1alexbel added a commit that referenced this issue Aug 28, 2024
@h1alexbel
feat(#124): 0.0.5
23f76ff
h1alexbel added a commit that referenced this issue Aug 28, 2024
@h1alexbel
feat(#124): fakehub.rs
5e435d5
h1alexbel added a commit that referenced this issue Aug 28, 2024
@h1alexbel
feat(#124): Fakehub::default()
893352b
h1alexbel added a commit that referenced this issue Aug 28, 2024
@h1alexbel
feat(#124): inversed too
dd1c8a1
h1alexbel added a commit that referenced this issue Aug 28, 2024
@h1alexbel
feat(#124): clean for cargo
ee7acc1
@h1alexbel h1alexbel mentioned this issue Aug 28, 2024
Merged
h1alexbel added a commit that referenced this issue Aug 29, 2024
@h1alexbel
feat(#124): no inversed, <uuid, github>
f0d2715
h1alexbel added a commit that referenced this issue Sep 2, 2024
@h1alexbel
feat(#124): one github
6f52d45
h1alexbel added a commit that referenced this issue Sep 2, 2024
@h1alexbel
feat(#124): register_in main
72439c4
h1alexbel added a commit that referenced this issue Sep 2, 2024
@h1alexbel
feat(#124): clean for cargo
72c5306
h1alexbel added a commit that referenced this issue Sep 2, 2024
@h1alexbel @l3r8yJ
feat(#124): uuid
d3ceed1 
Co-authored-by: Ivan Ivanchuk <[email protected]>
h1alexbel added a commit that referenced this issue Sep 2, 2024
@h1alexbel @l3r8yJ
feat(#124): Hub
02413c5 
Co-authored-by: Ivan Ivanchuk <[email protected]>
h1alexbel added a commit that referenced this issue Sep 2, 2024
@h1alexbel
feat(#124): FakeHub rename
eb68c7c
This was referenced Sep 2, 2024
Closed
Open
@0pdd
Copy link
Collaborator

0pdd commented Sep 2, 2024

@h1alexbel 2 puzzles #134, #135 are still not solved.

@0pdd
Copy link
Collaborator

0pdd commented Sep 3, 2024

@h1alexbel the puzzle #135 is still not solved; solved: #134.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@h1alexbel h1alexbel

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(#124): fakehub.rs, github.rs h1alexbel/fakehub
2 participants
@0pdd @h1alexbel