Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
ensembl
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
1
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
ensembl
Commits
18ad6df9
Commit
18ad6df9
authored
14 years ago
by
Andreas Kusalananda Kähäri
Browse files
Options
Downloads
Patches
Plain Diff
Fix SQL bugs.
parent
44af5d02
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
sql/patch_58_59_c.sql
+3
-3
3 additions, 3 deletions
sql/patch_58_59_c.sql
with
3 additions
and
3 deletions
sql/patch_58_59_c.sql
+
3
−
3
View file @
18ad6df9
...
...
@@ -15,9 +15,9 @@ ALTER TABLE splicing_event
#
Update
the
new
column
using
info
from
the
old
column
and
the
#
attrib_type
table
.
UPDATE
splicing_event
se
JOIN
attrib
ute
_type
at
ON
(
se
.
`type`
=
at
.
code
)
SET
se
.
attrib_type_id
=
at
.
attrib
ut
_type_id
WHERE
at
.
attrib
ut
_type_id
BETWEEN
300
AND
311
;
JOIN
attrib_type
at
ON
(
se
.
`type`
=
at
.
code
)
SET
se
.
attrib_type_id
=
at
.
attrib_type_id
WHERE
at
.
attrib_type_id
BETWEEN
300
AND
311
;
#
Drop
the
old
column
.
ALTER
TABLE
splicing_event
DROP
COLUMN
`type`
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
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