Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
categories
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
project-open
categories
Commits
02217349
Commit
02217349
authored
Mar 22, 2011
by
Frank Bergmann
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
- fixed syntax error from OpenACS
parent
94099492
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
7 additions
and
3 deletions
+7
-3
upgrade-1.1d1-1.1d2.sql
sql/postgresql/upgrade/upgrade-1.1d1-1.1d2.sql
+7
-3
No files found.
sql/postgresql/upgrade/upgrade-1.1d1-1.1d2.sql
View file @
02217349
-- source was undeclared.
-- fraber 110322: fixed syntax error from OpenACS?!?
create
or
replace
function
category_tree__copy
(
integer
,
-- source_tree
integer
,
-- dest_tree
...
...
@@ -24,6 +27,7 @@ begin
for source in (select category_id, parent_id, left_ind, right_ind from categories where tree_id = p_source_tree) loop
v_category_id := acs_object__new (
null,
''
category
''
, -- object_type
now(), -- creation_date
p_creation_user, -- creation_user
...
...
@@ -38,11 +42,11 @@ begin
end loop;
-- correct parent_ids
update categories
c
update categories
set parent_id = (select t.category_id
from categories s, categories t
where s.category_id = c.parent_id
and t.tree_id =
copy.
dest_tree
where s.category_id = c
ategories
.parent_id
and t.tree_id =
p_
dest_tree
and s.left_ind + v_new_left_ind = t.left_ind)
where tree_id = p_dest_tree;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment