This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I was wondering if it would it be possible to change the DataProviderAdapter from internal to public so that we can take advantage of the CreateCommand and CreateCommandBuilder functions? (having access to CommandRunner would be incredible helpful as well) It would be really helpful if we didn't have to rewrite the functionality available through these functions in order to use the PrepareCommand function. Thanks, Jason Moore |
|
|
|
|
No sorry we don't intend for this class to be a public part of LightSpeed so we want to keep this marked as internal. If you have a source license you can create a custom build which makes this change but keep in mind we cannot provide support for custom builds.
|
|
|
|
|
After doing more digging, I found lightSpeedContext.DataProviderObjectFactory.CreateCommand(), which solves half the battle! Now if I can find a way to use the CommandRunner.Execute function so that I can ensure all database access is consistently logged when a logger is configured on the LightSpeedContext I'll be golden! Would it be possible to add ExecuteNonQuery, ExecuteReader, ExecuteScalar functions to the UnitOfWork that take an IDbCommand? // I'm open to suggestions, I'm just looking for the best way to ensure consistent database access and logging. |
|
|
|
