Bug with bad proc names

Early Access Program for SQL Source Control

Moderators: Chris Auckland, David Atkinson, sherr

Bug with bad proc names

Postby AdamR » Wed Apr 07, 2010 4:53 pm

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)
AdamR
 
Posts: 13
Joined: Wed Apr 07, 2010 4:50 pm

Bug with bad proc names

Postby sherr » Thu Apr 22, 2010 10:18 pm

Hi,

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

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 :-)
SQL Source Control - Project Manager
sherr
 
Posts: 126
Joined: Thu Mar 19, 2009 12:45 pm
Location: Cambridge

Postby M. Kaptein » Fri Apr 23, 2010 3:56 pm

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.
M. Kaptein
 
Posts: 1
Joined: Fri Apr 23, 2010 3:50 pm

GO Table Alias

Postby sherr » Fri Apr 23, 2010 4:04 pm

We have been able to reproduce the GO alias problem here. Would it be possible to use a different alias for now?
sherr
 
Posts: 126
Joined: Thu Mar 19, 2009 12:45 pm
Location: Cambridge


Return to SQL Source Control EAP

Who is online

Users browsing this forum: No registered users and 0 guests