{"issue":{"milestone":null,"user":{"login":"Andorbal","id":579839,"url":"https://api.github.com/users/Andorbal","avatar_url":"https://secure.gravatar.com/avatar/676addadcb8b15cdfe8da34cf1159b9e?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"676addadcb8b15cdfe8da34cf1159b9e"},"title":"Identity insert for Sql Server","created_at":"2011-11-09T20:06:10Z","labels":[],"updated_at":"2011-12-19T15:56:44Z","state":"open","id":2190557,"pull_request":{"patch_url":"https://github.com/schambers/fluentmigrator/pull/185.patch","html_url":"https://github.com/schambers/fluentmigrator/pull/185","diff_url":"https://github.com/schambers/fluentmigrator/pull/185.diff"},"html_url":"https://github.com/schambers/fluentmigrator/issues/185","closed_at":null,"body":"I've added a method that will allow users of Sql Server to insert explicit identity data into tables with an identity field.  For all other database providers, the method is simply ignored.","number":185,"url":"https://api.github.com/repos/schambers/fluentmigrator/issues/185","comments":9,"assignee":null},"comment":{"user":{"login":"Andorbal","id":579839,"url":"https://api.github.com/users/Andorbal","avatar_url":"https://secure.gravatar.com/avatar/676addadcb8b15cdfe8da34cf1159b9e?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"676addadcb8b15cdfe8da34cf1159b9e"},"created_at":"2011-12-19T15:56:44Z","updated_at":"2011-12-19T15:56:44Z","id":3204924,"body":"You're correct that it's a hidden conditional, but including the conditional inside FM means that it can be applied consistently, tested fully, and can help remove a large amount of clutter in end users' code in exchange for a small amount of code in the library.\r\n\r\nMy comment from November 10th sums up why I think this hidden conditional would not be the same as most other SQL Server specific functions.","url":"https://api.github.com/repos/schambers/fluentmigrator/issues/comments/3204924"},"action":"created"}