-
Notifications
You must be signed in to change notification settings - Fork 61
Settlements Table Schema #808
Comments
/start |
Tips:
|
@GaryThisSidee This depends on the Credit and Debit table, you'd have to set up a constraint and make sure it can only have a credit id or a debit id (not both)
from the description: #787 (comment) Credit and Debit have to merged and then you need to add a function to create a table in |
ohh i see |
@seprintour looks like u already working on #811 should i do the #810 ? |
Yea, you can start working on it.. It also depends on #811 though.. There's a field for permitId |
Do you have any updates @GaryThisSidee? If you would like to release the bounty back to the DevPool, please comment |
@GaryThisSidee - Releasing the bounty back to dev pool because the allocated duration already ended! |
+ Evaluating results. Please wait... |
@pavlovcik the deadline is at 2024-02-17T12:34:34.314Z |
+ Evaluating results. Please wait... |
Settlements
Represents the overarching record of a financial activity. Each entry can have references to either a credit or a debit.
id
created
updated
user_id
id
of the user penalized.org_id
id
of the organization.repo_id
id
of the repository where the issue is located.issue_id
id
of the issue related to the penalty.credit_id
debit_id
The text was updated successfully, but these errors were encountered: