Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
MaarchCourrier
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Redmine
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Harbor Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Maarch
MaarchCourrier
Commits
966cf200
Commit
966cf200
authored
13 years ago
by
Cyril Vazquez
Browse files
Options
Downloads
Patches
Plain Diff
No commit message
No commit message
parent
27b67095
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
core/trunk/structure.sql
+1
-0
1 addition, 0 deletions
core/trunk/structure.sql
with
1 addition
and
0 deletions
core/trunk/structure.sql
+
1
−
0
View file @
966cf200
...
@@ -1193,6 +1193,7 @@ CREATE TABLE notif_event_stack
...
@@ -1193,6 +1193,7 @@ CREATE TABLE notif_event_stack
table_name
character
varying
(
32
)
NOT
NULL
,
table_name
character
varying
(
32
)
NOT
NULL
,
record_id
character
varying
(
255
)
NOT
NULL
,
record_id
character
varying
(
255
)
NOT
NULL
,
event_date
timestamp
without
time
zone
NOT
NULL
,
event_date
timestamp
without
time
zone
NOT
NULL
,
event_info
character
varying
(
255
)
NOT
NULL
,
exec_date
timestamp
without
time
zone
NOT
NULL
,
exec_date
timestamp
without
time
zone
NOT
NULL
,
exec_result
character
varying
(
50
)
NOT
NULL
,
exec_result
character
varying
(
50
)
NOT
NULL
,
CONSTRAINT
notif_event_stack_pkey
PRIMARY
KEY
(
system_id
)
CONSTRAINT
notif_event_stack_pkey
PRIMARY
KEY
(
system_id
)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment