Activity overview
Latest activity by wpostma
It was a fundamental mistake to embed a Git library in RSSC
Here are seven reasons why it was a fundamental engineering mistake to embed a C#-git-client library in RedGate SQL Source Control 4:
1. You can't keep up to date for new git versions.
2. You have ...
Transaction usage in SQL Source control is bad.
We have the problem that if you could fetch and apply one migration script at a time, you can be okay, but when you are three or four updates behind, redgate sql source control has the following ru...
It's broken again! :-)
Latest SQL Source Control frequently updated is broken again, in SQL 2016 RC1.
It's also a bit disconcerting that the fix that makes it compatible with SQL 2016 RC0 makes it incompatible with prior CTP versions. Whatever is going on in there sounds a bit scary.
W / comments
It's broken again! :-)
Latest SQL Source Control frequently updated is broken again, in SQL 2016 RC1.
It's also a bit disconcerting that the fix that makes it compatible with SQL 2016 RC0 makes it ...
As soon as we can get it we'll try it out. Meanwhile that's all we need to know.
W / comments
As soon as we can get it we'll try it out. Meanwhile that's all we need to know.
W
You know what would be great is if you open a ticket you post a link to that ticket here. I know. I'm smokin' weed right? Talking crazy?
Just an idea. Did some ticket get opened? Who knows.
Anyone with questions can contact me directly at wpostma at company dot com, and I work at a company called ramsoft. / comments
You know what would be great is if you open a ticket you post a link to that ticket here. I know. I'm smokin' weed right? Talking crazy?
Just an idea. Did some ticket get opened? Who knows.
Anyo...
sourcecontrol 4.2 worked with sql 2016 ctp but broke on RC0
I updated a dev workstation to SQL SERVER 2016 RC0 yesterday, and now I see this error in the commit changes dialog of SQL Source Control
Invalid column name 'remote_data_archive_migration_state'.
...
I can't see the ticket you opened, and I don't know how to log into the redgate support thing. / comments
I can't see the ticket you opened, and I don't know how to log into the redgate support thing.
To reproduce you will need SQL server 2016 CTP 3.3. Create this table, and commit it into SQL Source control: SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Group](
[InternalGroupID] [BIGINT] IDENTITY(1,1) NOT NULL,
[InternalRoleID] [BIGINT] NOT NULL,
[GroupName] [NVARCHAR](64) NOT NULL,
[ExtJson] [NVARCHAR](MAX) NULL,
CONSTRAINT [PK_Group] PRIMARY KEY CLUSTERED
( [InternalGroupID] ASC ) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
After that commit, go to another working copy (another user's machine with SQL Source control) and try to fetch the changes and apply them.
After that, run this tsql to add the constraint which contains an expression in the form ( isjson([ExtJSON])> 0): ALTER TABLE [dbo].[Group] WITH CHECK ADD CONSTRAINT [GROUP_ExtJSON_VALID] CHECK ( isjson([ExtJSON])> 0)
GO
ALTER TABLE [dbo].[Group] CHECK CONSTRAINT [GROUP_ExtJSON_VALID]
GO
Now commit that change on working copy on workstation 1. This commit should only contain the above extjson validation constraint and its check enable.
Now go back to workstation 2 and try to update.
Expectation:
ALTER TABLE [dbo].[Group] WITH CHECK ADD CONSTRAINT [GROUP_ExtJSON_VALID] CHECK ( isjson([ExtJSON])> 0)
GO
Actual:
ALTER TABLE [dbo].[Group] WITH CHECK ADD CONSTRAINT [GROUP_ExtJSON_VALID] CHECK ( [isjson]([ExtJSON])> 0)
GO
You can see an extra set of brackets. / comments
To reproduce you will need SQL server 2016 CTP 3.3. Create this table, and commit it into SQL Source control:SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Grou...
ISJSON constraints should not be escaped.
Your BRACKET_ALL_THE_THINGS() function needs an EXCEPTION encoded so that JSON validation Constraints like this do not get rewritten:
ALTER TABLE [PHI].[Study] ADD CONSTRAINT [PHI_STUDY_ExtJSON_VAL...
Why can't I undo (revert) filter edits?
It's a big pain in the buttinski that I can't right click on an Filter Edit change and revert it. The Revert (Undo Changes) menu item is grayed out.
Why is that? Please fix this. This is using la...