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

[Feature]: Implement database handler #1

New issue
Closed
opened 2024-11-13 14:50:40 -03:00 by anavarro · 0 comments
anavarro commented 2024-11-13 14:50:40 -03:00
Member
Copy link

Type of Feature

✨ New Feature

Description

Implement the basic database connections and methods.

Completion criteria

  • Implement an API that receives a database handler and returns a struct with a high level implementation of the library
  • Bootstrap database initialization if is not found
  • Implement graph like functionality
    • CRUD node, a node should be marshall from a user provided struct which implements an interface
    • CRUD edge, this should be from one node to another (Ex: node_a.setEdge(node_b, 'belogns_to', args)

Additional Information

No response

### Type of Feature ✨ New Feature ### Description Implement the basic database connections and methods. ### Completion criteria - [x] Implement an API that receives a database handler and returns a struct with a high level implementation of the library - [x] Bootstrap database initialization if is not found - [x] Implement graph like functionality - CRUD node, a node should be marshall from a user provided struct which implements an interface - CRUD edge, this should be from one node to another (Ex: `node_a.setEdge(node_b, 'belogns_to', args`) ### Additional Information _No response_
anavarro added the
Priority
Critical
Severity
High
Type
Feature
Status
Accepted
 labels 2024-11-13 14:50:40 -03:00
anavarro added this to the v0.1.0 - [E]TL milestone 2024-11-13 14:55:28 -03:00
anavarro started working 2024-11-13 14:55:30 -03:00
anavarro stopped working 2024-11-18 13:27:09 -03:00
4 days 22 hours
This repository is archived. You cannot comment on issues.
development
Branches Tags
Clear current reference
main
Clear current reference
No results found.
Labels
Clear labels
  
Outtakes/Blog Post

This can be used as a blog post content

  
Outtakes/Research

This can be further investigated

  
Outtakes/Resource

This can be used as a wiki resource

  
Priority
Critical
Do it now

  
Priority
High
Do it next

  
Priority
Low
It may be done

  
Priority
Medium
Do it when posible

  
Severity
Critical
Is provocking harmfull behavior

  
Severity
High
Is blocking or un-usable

  
Severity
Low
Is inconvinient

  
Severity
Medium
Is Broken with a workarround

  
Status
Abandoned
Work has been done but later abandoned

  
Status
Accepted
This has been reviwed and accepted

  
Status
Blocked
Something is blocking this

  
Status
Need More Info
Research or feedback is required to continue

  
Status
Out Of Scope
This is out of the [current] scope

  
Status
Pending
In waiting of evaluation

  
Status
Won't do
This will not be implemented

  
Type
Bug
Something is not working

  
Type
Documentation
Documentation changes

  
Type
Feature
New functionality

  
Type
Idea
Just an idea for now

  
Type
Testing
Needs testing

No labels
Outtakes/Blog Post
Outtakes/Research
Outtakes/Resource
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Severity
Critical
Severity
High
Severity
Low
Severity
Medium
Status
Abandoned
Status
Accepted
Status
Blocked
Status
Need More Info
Status
Out Of Scope
Status
Pending
Status
Won't do
Type
Bug
Type
Documentation
Type
Feature
Type
Idea
Type
Testing
Milestone
Clear milestone
No items
No milestone
v0.1.0 - [E]TL
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Total time spent: 4 days 22 hours
anavarro
4 days 22 hours
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: alecodes/synchronizator-go#1
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?