From: Peter Rabbitson Date: Sun, 6 Sep 2009 21:58:22 +0000 (+0000) Subject: Fix mssql pod X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c84189e13c678016a72cf3163730b7705b97a959;p=dbsrgits%2FDBIx-Class-Historic.git Fix mssql pod --- diff --git a/lib/DBIx/Class/Storage/DBI/MSSQL.pm b/lib/DBIx/Class/Storage/DBI/MSSQL.pm index 886b6fe..d528b22 100644 --- a/lib/DBIx/Class/Storage/DBI/MSSQL.pm +++ b/lib/DBIx/Class/Storage/DBI/MSSQL.pm @@ -221,13 +221,15 @@ This is more dangerous, as inserting into a table with an on insert trigger that inserts into another table with an identity will give erroneous results on recent versions of SQL Server. -=head2 bulk_insert +=head2 identity insert Be aware that we have tried to make things as simple as possible for our users. -For MSSQL that means that when a user tries to do a populate/bulk_insert which -includes an autoincrementing column, we will try to tell the database to allow -the insertion of the autoinc column. But the user must have the db_ddladmin -role membership, otherwise you will get a fairly opaque error message. +For MSSQL that means that when a user tries to create a row, while supplying an +explicit value for an autoincrementing column, we will try to issue the +appropriate database call to make this possible, namely C. Unfortunately this operation in MSSQL requires the +C privilege, which is normally not included in the standard +write-permissions. =head1 AUTHOR