我有一些代码，我以这种方式编码，以实现高可维护性和代码重用性。我担心一段特定的代码，如果这段代码在高压力下崩溃，我想就专业意见。
public abstract class PlexxisDataTransferObjects : PlexxisDatabaseRow
{
//static methods
public static List<PlexxisDatabaseRow> GetAll();
//Constructors
public PlexxisDataTransferObjects(){ }
//Methods
public abstract bool Insert(OracleConnection Conn);
public abstract bool Update(OracleConnection Conn);
public abstract bool Delete(OracleConnection Conn);
public bool Insert()
{
using (var Conn = new OracleConnection(ConnectionString))
{
Conn.Open();
return Insert(Conn);
}
}
public bool Update()
{
using (var Conn = new OracleConnection(ConnectionString))
{
Conn.Open();
return Update(Conn);
}
}
public bool Delete()
{
using (var Conn = new OracleConnection(ConnectionString))
{
Conn.Open();
return Delete(Conn);
}
}
}
//Data Transfer Objects
public sealed class Apps : PlexxisDataTransferObjects
{
//Static Methods
public override static List<PlexxisDatabaseRow> GetAll()
{
List<PlexxisDatabaseRow> collection = new List<PlexxisDatabaseRow>();
using (var Conn = new OracleConnection(ConnectionString))
{
using (var Command = new OracleCommand("select * from APPS", Conn))
{
Conn.Open();
using (var reader = Command.ExecuteReader(CommandBehavior.CloseConnection))
while (reader.Read())
collection.Add(new Apps(reader));
}
}
return collection;
}
//Fields
public int AppId;
public string AuthKey;
public string Title;
public string Description;
public bool isClientCustomApp;
//Constructors
public Apps() : base () { }
public Apps(OracleDataReader reader) : base ()
{
if (reader["APP_ID"] != DBNull.Value)
this.AppId = Convert.ToInt32(reader["APP_ID"]);
if (reader["AUTH_KEY"] != DBNull.Value)
this.AuthKey = Convert.ToString(reader["AUTH_KEY"]);
if (reader["TITLE"] != DBNull.Value)
this.Title = Convert.ToString(reader["TITLE"]);
if (reader["DESCRIPTION"] != DBNull.Value)
this.Description = Convert.ToString(reader["DESCRIPTION"]);
if (reader["IS_CLIENT_CUSTOM_APP"] != DBNull.Value)
this.isClientCustomApp = Convert.ToBoolean(reader["IS_CLIENT_CUSTOM_APP"]);
}
//Methods
public override bool Insert(OracleConnection Conn)
{
string sql = string.Empty;
sql += "INSERT INTO APPS (APP_ID, AUTH_KEY, TITLE, DESCRIPTION, IS_CLIENT_CUSTOM_APP)";
sql += "VALUES(:appid, :authkey, :title, :description, :iscust)";
using (var Command = new OracleCommand(sql, Conn))
{
AppId = GetId();
Command.Parameters.Add(":appid", OracleDbType.Int32).Value = AppId;
Command.Parameters.Add(":authkey", OracleDbType.Varchar2).Value = AuthKey;
Command.Parameters.Add(":title", OracleDbType.Varchar2).Value = Title;
Command.Parameters.Add(":description", OracleDbType.Varchar2).Value = Description;
Command.Parameters.Add(":iscust", OracleDbType.Int32).Value = Convert.ToInt32(isClientCustomApp);
return Convert.ToBoolean(Command.ExecuteNonQuery());
}
}
public override bool Update(OracleConnection Conn)
{
string sql = string.Empty;
sql += "UPDATE APPS SET ";
sql += "AUTH_KEY = :authkey, TITLE = :title, DESCRIPTION = :description, IS_CLIENT_CUSTOM_APP = :iscust ";
sql += "WHERE APP_ID = :appid";
using (var Command = new OracleCommand(sql, Conn))
{
Command.Parameters.Add(":authkey", OracleDbType.Varchar2).Value = AuthKey;
Command.Parameters.Add(":title", OracleDbType.Varchar2).Value = Title;
Command.Parameters.Add(":description", OracleDbType.Varchar2).Value = Description;
Command.Parameters.Add(":iscust", OracleDbType.Int32).Value = Convert.ToInt32(isClientCustomApp);
Command.Parameters.Add(":appid", OracleDbType.Int32).Value = AppId;
return Convert.ToBoolean(Command.ExecuteNonQuery());
}
}
public override bool Delete(OracleConnection Conn)
{
string sql = string.Empty;
sql += "DELETE FROM APPS ";
sql += "WHERE APP_ID = :appid";
using (var Command = new OracleCommand(sql, Conn))
{
Command.Parameters.Add(":appid", OracleDbType.Int32).Value = AppId;
return Convert.ToBoolean(Command.ExecuteNonQuery());
}
}
}
最让我担心的是抽象类中的Insert，Update和Delete方法，它在具体类中调用Insert，Update和Delete。
我已经这样做了，这样我就可以在必要时通过打开连接并显式启动事务来启用事务，发送事务并且仍然让对象执行他们需要做的事情;此外，如果我必须为40个左右的类明确重写3个方法，它可能变得非常麻烦。
但是，我担心通过尽早打开连接可能会占用数据库。我不知道在任何给定时间可能有多少输入数据被更新。在这种情况下，我有两个主要想法，我可以在抽象类中进行插入，更新和删除抽象，并在Command.ExecuteNonQuery（）之前显式打开连接时实现它们，或者我可以保留它现在的样子。
首先，您对此情况的看法。其次指出逻辑背后的任何陷阱或你碰巧发现的任何不良编码也会非常有帮助。
答案 0 :(得分：3)
我认为调查工作单元模式可能是值得的。
对我来说，看起来你已经在使用活动记录模式，但是我发现它的问题（从关注点和依赖关系的角度分离）你的类定义是硬编码的，依赖于oracle，这意味着使用您的DTO的代码也必须依赖于oracle。我并不是说如果你想切换你的数据库就是一个问题，我说最好有一个非常分离的系统，用于理解和单元测试。
class Application
{
public int ID { get; set; }
public string AuthKey { get; set; }
// and so on
}
interface IApplicationRepository
{
IEnumerable<Application> GetAll();
void Update(Application app);
void Delete(Application app);
void Insert(Application app);
}
interface IUnitOfWork : IDisposable
{
IApplicationRepository Applications { get; }
void Commit();
}
void SaveButton_Click(object sender, EventArgs e)
{
// this could be resolved by dependency injection, this would know about Oracle
using (var uow = UnitOfWorkFactory.Create())
{
uow.Applications.Insert(new Application { AuthKey = "1234" });
// you may have other repo that have work done in the same transaction / connection
uow.Commit();
}
}
如果你看一下上面写的所有代码，就没有提到Oracle，甚至没有提到连接或事务的概念。你有这个名为UnitOfWork的抽象，它在幕后为你的应用程序管理状态。存储库适用于普通类。这种类型的代码很容易模拟和编写测试。这对于可维护性来说是巨大的。
class OracleApplicationRepository : IApplicationRepository
{
public readonly OracleDbConnection _dbConnection;
public OracleApplicationRepository(OracleDbConnection dbConnection)
{
_dbConnection = dbConnection;
}
IEnumerable<Application> GetAll()
{
// up to you, the viewer
throw new NotImplementedException();
}
void Update(Application app)
{
// up to the viewer
}
void Delete(Application app)
{
// up to the viewer
}
void Insert(Application app)
{
using (var command = _dbConnection.CreateCommand())
{
// or whatever the syntax is
command.Parameters["AuthKey"] = app.AuthKey;
command.ExecuteNonQuery();
}
}
}
class OracleUnitOfWork : IUnitOfWork
{
private readonly OracleDbConnection _dbConnection;
public OracleUnitOfWork(string connectionString)
{
_dbConnection = new OracleDbConnection(connectionString);
}
public IApplicationRepository Applications
{
get
{
// this could be lazy loaded instead of making new instances all over the place
return new OracleApplicationRepository(_dbConnection);
}
}
public Dispose()
{
// close the connection and any transactions
_dbConnection.Dispose();
}
}
答案 1 :(得分：0)
如果要循环遍历大量数据，则打开和关闭每个CRUD操作的数据库连接将会受到影响。此外，你应该使用try，catch，最后。您不能保证数据库将启动，它将导致抛出异常。