…r ALTER DATABASE in SANDBOX3_GBL.sql

Unit tests were failing

…ngth as -1

…leTypes

if there is an nvarchar(max) in a table type, we should output the length as -1

Escape usernames

Fix nvarchar(max) in table types, and escape user names

fixes #34

Allow specifying a connection string in the console

I’m trying to use SchemaZen for a database whose name contains a dot
(i.e. `MyDatabase.Dev`). Presently it fails because the DB names are
not being escaped (with square brackets) correctly. This fixes that.

Escape DB names correctly

…nows whether it's asc or desc

Support descending indexes

Add support for constraint filters

# Conflicts:
#	model/Database.cs

Add support for table indexes with filters

Csh add support for roles

Change ordder of execution

Delete empty tsv files that represent empty tables

Revert "Add support for table indexes with filters"

This reverts commit f8ace14.

Just realized the test that was failing was not an existing test.

This test was never passing. Deleting it.

…umns

Support View Indexes with multiple columns

…g to a previous script.

… to a previous script.

…e CASCADE is picked up by non-cascading FKs if another FK with same name in different schema is CASCADE

…ete are correct

FKs ordering not consistent in script file

Constraint ordering not consistent in script file

Fk same name on up on del

Don't be case sensitive for user matching

ASC is the default so it isn't necessary to specify it.
Doing so causes unwanted diffs for people who use SchemaZen for db
version control.

…c-master

I removed this behavior as ASC is the default.

Csh file paths

Add support for sysname type

Added parameter filterTypes to schemazen script command

Improve error message

Mvs create schemazen library

user defined types

user defined types first

Fix for permission set + tests

# Conflicts:
#	model/Models/Database.cs

Created Schemazen library project

Fixes #96

… added directly after the trigger definition with no new line.

…sn't tacked onto teh end of the definition when there are no SETs

Trigger script without SETs produces invalid script

…rigger

Enable Test "TestScriptViewInsteadOfTrigger"

* String interpolation in favor of string format or concatenation.
* Public fields converted to properties.
* Auto Initialized properties where applicable.
* Refactored SqlAssembly.ScriptCreate to be more readable.
* Renamed private fields to start with "_".

The tests explain the problem. Thanks @Nazgul07 for reporting.

fixes #107

#105

#108