Comments
Sort by recent activity
Brian,
thanks for your help - my direct report with Red-Gate support has resulted in a case (F0033534) being worked on already. I sent Chris Auckland some error logs and observations - hope he'll be able to figure out the root cause of this problem somehow - I'm confident he will !
Thanks!
Marc / comments
Brian,
thanks for your help - my direct report with Red-Gate support has resulted in a case (F0033534) being worked on already. I sent Chris Auckland some error logs and observations - hope he'll b...
Anu Deshpande wrote:
But SQL Prompt doesn't add the computed columns in 'insert into' statements.
Ah - yes it does ! (but it shouldn't)
Try this: SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[DocumentStore](
[ID] [int] IDENTITY(1,1) NOT NULL PRIMARY KEY,
[DocFileName] [varchar](255) NULL,
[DocContent] [image] NULL,
[DocLength] AS (datalength([DocContent])) PERSISTED,
)
GO
SET ANSI_PADDING OFF
GO
When I go ahead and type INSERT INTO dbo.DocumentStore
and how I press <ENTER> on my keyboard, this gets expanded into: INSERT INTO dbo.DocumentStore
( DocFileName ,
DocContent ,
DocLength
)
VALUES ( '' , -- DocFileName - varchar(255)
NULL , -- DocContent - image
0 -- DocLength - int
)
and quite clearly, the "DocLength" column is a computed column and there's really absolutely no point for me to insert a value into that column!
SQL Prompt 4.0.3.10 on SQL Server 2008 / comments
Anu Deshpande wrote:
But SQL Prompt doesn't add the computed columns in 'insert into' statements.
Ah - yes it does ! (but it shouldn't)
Try this:SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
SET ...
Anu Deshpande wrote:
Ah ha I see what is happening!
Can you kindly update your version to 4.0.4.11?
Kindly let me know whether it fixes the issue or not.
Yes, that definitely solves that problem - thanks!
Marc / comments
Anu Deshpande wrote:
Ah ha I see what is happening!
Can you kindly update your version to 4.0.4.11?
Kindly let me know whether it fixes the issue or not.
Yes, that definitely solves that probl...
Thorsten,
I've been pestering Red Gate about this behavior ever since they took over SQL Prompt - without any success, so far :-( Glad to see another user also seems to agree this is an issue that needs to be fixed ASAP.
See this thread here - an "enhancement request" has already been logged - express your interest in it, then we might get them to finally fix it some day!! http://www.red-gate.com/MessageBoard/vi ... php?t=9434 / comments
Thorsten,
I've been pestering Red Gate about this behavior ever since they took over SQL Prompt - without any success, so far :-( Glad to see another user also seems to agree this is an issue that...
This issue seems to have been fixed with this new cummulative patch release: http://www.red-gate.com/MessageBoard/vi ... hp?t=10248
At least in my cases, everything works as expected now, with this new patch version. / comments
This issue seems to have been fixed with this new cummulative patch release:http://www.red-gate.com/MessageBoard/vi ... hp?t=10248
At least in my cases, everything works as expected now, with this ...
I agree - having computed columns in the list of fields of an expanded INSERT statement makes no sense at all.
Same goes for columns of type TIMESTAMP or ROWVERSION - one can never insert a value into those - so why put them in the list of fields of an INSERT statement in the first place?? / comments
I agree - having computed columns in the list of fields of an expanded INSERT statement makes no sense at all.
Same goes for columns of type TIMESTAMP or ROWVERSION - one can never insert a value i...