Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Issue when running Create_Procs.sql

web-app

Hi,

I keep getting the following error when I run Createprocs.sql:

Cannot add rows to sysdepends for the current stored procedure because it depends on the missing object 'geminiprojreposdeletenode'. The stored procedure will still be created.

I received a similar error for another proc but was able to fix it by running the "If exists drop and recreate" portion of the query.  I've tried the same with 'geminiprojreposdeletenode'  First I run the BLUE portion of the query below and that returns without an error. I run the RED portion of the query immediately after and I get the same error as above in purple.

/*********************************************************
* Deletes a node for a project. WOW SQL recursion!!!
* used on project repository home page.
*********************************************************/

if exists(select name from sysobjects where name='geminiprojreposdeletenode')
 drop procedure geminiprojreposdeletenode
go

create procedure geminiprojreposdeletenode
 @projid numeric(10,0),
 @nodeid numeric(10,0)
as
begin
begin transaction

declare @nNodeID numeric(10,0)
declare CurNodes cursor local readonly for select nodeid from projectrepository where parentnodeid=@nodeid and projid=@projid

open CurNodes

fetch next from CurNodes into @nNodeID

while @@fetchstatus=0
begin
 exec gemini_projreposdeletenode @projid,@nNodeID
 fetch next from CurNodes into @nNodeID
end

delete from projectrepository where parentnodeid=@nodeid and projid=@projid
delete from projectrepository where nodeid=@nodeid and projid=@projid
 

close CurNodes
deallocate CurNodes

commit transaction
end
go

I can't seem to figure out why I'm getting the error.  Has anyone else had this occur?

Thank you.

Jim

jimjimlit
· 1
jimjimlit
Replies (1)
helpful
0
not helpful

Hi Jim,

These are only warnings and can be safely ignored.

The reason you keep getting it for this stored procedure is because it is dependant on itself (recursive).


Mark Wing
· 9108
Mark Wing