viagogo / sqlcomparer Goto Github PK

Right now we're just saying something went wrong -- expand by saying what the new tree looks like (that failed to parse)

From @Vannevelj on July 29, 2016 13:7

Copied from original issue: viagogo/SQLComparerInternal#11

From @Vannevelj on August 3, 2016 9:3

proc | Dev QA Prod | QA Prod Dev | Prod QA Dev
proc1| V V X

For example. Or:

proc | Dev QA Prod | Dev QA | QA Prod

Copied from original issue: viagogo/SQLComparerInternal#26

From @Vannevelj on July 29, 2016 13:7

Copied from original issue: viagogo/SQLComparerInternal#9

From @Vannevelj on July 29, 2016 13:6

Copied from original issue: viagogo/SQLComparerInternal#8

From @Vannevelj on August 4, 2016 13:39

• Right now we only compare the first 10 procs. that's unacceptable.
• Stop doing the naive comparison where we match everything, even dev & dev.
• Caching? Although might not be necessary once we do smarter comparison
• Single sql connection that retrieves all necessary data at once instead of a separate request for each proc

Copied from original issue: viagogo/SQLComparerInternal#43

From @Vannevelj on August 1, 2016 9:24

Copied from original issue: viagogo/SQLComparerInternal#17

From @Vannevelj on July 29, 2016 13:7

Copied from original issue: viagogo/SQLComparerInternal#10

From @Vannevelj on July 29, 2016 13:8

Copied from original issue: viagogo/SQLComparerInternal#13

From @olamackow on August 4, 2016 12:58

Copied from original issue: viagogo/SQLComparerInternal#39

Maybe this should be turned into a partial that you can just include on each page?

From @Vannevelj on August 3, 2016 16:50

investigate closer.

PS: do they get logged properly?

Copied from original issue: viagogo/SQLComparerInternal#30

Don't do it for, for example, create clustered index statements.

Given two environments:

• A
• B

And a proc that exists only in B, if I attempt to push the proc from B to A the process fails (it attempts to alter rather than create). I believe this is a 'right to left' push.

Example: data and data_dev

Given 3 environments:

• A
• B
• C

If I create a proc in A and search for it, I'm told the proc doesn't exist.

From @Vannevelj on August 5, 2016 12:9

Copied from original issue: viagogo/SQLComparerInternal#58

From @Vannevelj on August 1, 2016 14:10

Rather than the double [success, message] thing

Copied from original issue: viagogo/SQLComparerInternal#22

Sometimes you just want to easily see how a proc is defined.

From @Vannevelj on August 4, 2016 16:11

Right now it's redirected to Index

Copied from original issue: viagogo/SQLComparerInternal#46

From @Vannevelj on August 4, 2016 15:2

Now it's just \r\n

Copied from original issue: viagogo/SQLComparerInternal#45

From @Vannevelj on August 5, 2016 10:40

Right now all messages are shown with a success banner. We should probably use a second TempData property to indicates success or failure.

Copied from original issue: viagogo/SQLComparerInternal#54

From @Vannevelj on August 2, 2016 16:55

Copied from original issue: viagogo/SQLComparerInternal#24

From @Vannevelj on July 29, 2016 13:6

Copied from original issue: viagogo/SQLComparerInternal#7

From @Vannevelj on August 4, 2016 10:4

Copied from original issue: viagogo/SQLComparerInternal#36

From @Vannevelj on August 5, 2016 14:15

Display only. This will save a lot of space in the comparison view and help put lines of code on one line

Copied from original issue: viagogo/SQLComparerInternal#60

Occurs when DB exists in some of the environments selected but not all

I believe we do a replace of the create token when we encounter create procedure -- with the release of create or alter procedure that would cause some issues

From @Vannevelj on August 5, 2016 10:3

People should know that it is in the form of db.schema.name

Copied from original issue: viagogo/SQLComparerInternal#52

From @olamackow on August 4, 2016 12:57

Copied from original issue: viagogo/SQLComparerInternal#38

From @Vannevelj on August 3, 2016 16:49

Copied from original issue: viagogo/SQLComparerInternal#29