Red Gate forums :: View topic - Bug with bad proc names
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Source Control EAP
SQL Source Control EAP forum

Bug with bad proc names

Search in SQL Source Control EAP forum
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.
Jump to:  
Author Message
AdamR



Joined: 07 Apr 2010
Posts: 13

PostPosted: Wed Apr 07, 2010 4:53 pm    Post subject: Bug with bad proc names Reply with quote

So, this is bad development, but someone put a proc named dbo.USPEmp#. I get all sorts of errors now because of the # sign in the when getting latest updates or trying to delete and commit.

Failed to update:
#oEc.#8Jf: Errors occured whilst parsing file C:\Users\adamr\AppData\Local\Red Gate\SQL Source Control 0\WorkingBases\b3ae1b30-6f18-4d35-a002-1daa9b3501b5\Stored Procedures\dbo.uspEmp#.sql
'line 5:34: unexpected token: ["#",<735>,line=5,col=34] [char=85]'
---> #Eyg.#Lyg: Errors occured whilst parsing file C:\Users\adamr\AppData\Local\Red Gate\SQL Source Control 0\WorkingBases\b3ae1b30-6f18-4d35-a002-1daa9b3501b5\Stored Procedures\dbo.uspEmp#.sql
'line 5:34: unexpected token: ["#",<735>,line=5,col=34] [char=85]'
---> line 5:34: unexpected token: ["#",<735>,line=5,col=34] [char=85]
--- End of inner exception stack trace ---
at #oEc.#7Jf.#t.#B3.#sKf()
at #oEc.#7Jf.#gKf(Action action)
--- End of inner exception stack trace ---

Server stack trace:
at RedGate.SQLSourceControl.Engine.Cancellables.CancellableOperation.#t.#izb.#j5f()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:
at RedGate.SQLSourceControl.CommonUI.Forms.ErrorDialog.DoWithObviousExceptionsThrowAll(Action action)
at #JLc.#PLc.#CTc(ICancellableOperation`1 operation, Object token)
Back to top
View user's profile Send private message
sherr



Joined: 19 Mar 2009
Posts: 125
Location: Cambridge

PostPosted: Thu Apr 22, 2010 10:18 pm    Post subject: Bug with bad proc names Reply with quote

Hi,

We are currently working on this issue. It's surprising how many people have # in their db object names... Smile

Would you be able to email us a copy of the dbo.USPEmp# to SqlSourceControlSupport@red-gate.com? This way, we could recreate the exact issue that you are having and test it internally. This will only be used for our internal test purposes.

Our internal reference number is SOC-599.

Thanks for your help!
Stephanie M. Herr Smile
SQL Source Control - Project Manager
Back to top
View user's profile Send private message
M. Kaptein



Joined: 23 Apr 2010
Posts: 1

PostPosted: Fri Apr 23, 2010 3:56 pm    Post subject: Reply with quote

We encountered a simular problem with a table alias named [go] The parser didn't expect this and interpreted it as the SSMS keyword GO.
Back to top
View user's profile Send private message
sherr



Joined: 19 Mar 2009
Posts: 125
Location: Cambridge

PostPosted: Fri Apr 23, 2010 4:04 pm    Post subject: GO Table Alias Reply with quote

We have been able to reproduce the GO alias problem here. Would it be possible to use a different alias for now?
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies. All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group