Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
Script recalcul calque
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
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
ERASME
Script recalcul calque
Commits
09fd4e17
Commit
09fd4e17
authored
2 years ago
by
Pierre-Gilles LEVALLOIS
Browse files
Options
Downloads
Patches
Plain Diff
fix truncate sql order
parent
569f1501
Branches
Branches containing commit
Tags
Tags containing commit
1 merge request
!6
Fully functional version that calculate layer with all stages
Pipeline
#59895
passed
2 years ago
Stage: Build Calqul
Stage: Deploy Calqul Buttons
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Dockerfiles/python/scripts/utils.py
+1
-1
1 addition, 1 deletion
Dockerfiles/python/scripts/utils.py
with
1 addition
and
1 deletion
Dockerfiles/python/scripts/utils.py
+
1
−
1
View file @
09fd4e17
...
...
@@ -334,7 +334,7 @@ def truncateDataInDB(DB_params, DB_schema, tableName):
conn
,
cur
=
connectDB
(
DB_params
)
# Build request
truncateQuery
=
"
TRUNCATE TAB
A
LE
"
+
DB_schema
+
"
.
"
+
tableName
truncateQuery
=
"
TRUNCATE TABLE
"
+
DB_schema
+
"
.
"
+
tableName
# Execute query
cur
.
execute
(
truncateQuery
)
...
...
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