public StoredProcedure(Schema schema, String name, Int32 versionNumber, SqlParameter[] sqlParameters)
: this()
{
this.Schema = schema;
this.Name = IdentifierHelper.GetStrippedSqlIdentifier(name);
this.VersionNumber = versionNumber;
this.SqlParameters = sqlParameters;
this.DoesReturnResultSet = true;
this._configuration = this.Schema.Database.Server.Configuration;
}
public Server(Configuration configuration)
: base()
{
IdentifierHelper.Init(configuration);
this.Configuration = configuration;
}
private Column(Configuration configuration, String name)
: this()
{
this.Name = IdentifierHelper.GetStrippedSqlIdentifier(name);
this._configuration = configuration;
}
/// A third reason is that the code providers' IsValidIdentifier() doesn't recognize all of the keywords/reserved words I think it should, like all of the
/// LINQ keywords, and new keywords like C#'s async and await. (I understand these aren't really keywords, but they certainly shouldn't
/// be treated as valid identifiers).</para>
/// <para>The result of these drawbacks is this method, coupled with a lengthy list of keywords, reserved words, and
/// any other words that shouldn't be used as identifiers in C#, VB, or F#.</para>
/// </summary>
/// <param name="sqlIdentifier"></param>
/// <returns></returns>
public static String GetTargetLanguageIdentifier(String sqlIdentifier)
{
if (!_isInitialized)
throw new Exception(Properties.Resources.IdentiferHelperInitNotCalled);
sqlIdentifier.Name("sqlIdentifier").NotNullEmptyOrOnlyWhitespace();
