Hello - did u ever think about refactor ArachnodeDAO to interface without dependency on DataTableAdapters. Your implementation with table adapter in that case will be one of option.
Below u'll find my propose to interface:
IArachnodeDAO {void DeleteCrawlRequest(string absoluteUri1, string absoluteUri2)void DeleteDiscoveries()... List<DataType> GetAllowedDataTypes();List<ACrawlAction> GetCrawlActions();...
}
After that refactoring arachnode.net would be elastic application without dependency on mssql database.
best regards
That would be a nice option.
There are a few things to consider when performing such a refactor.
1.) Data validation is performed by the DataTableAdapters.
2.) There is logic in the MS-SQL database that would have to be replicated to, say, MySQL.
3.) There is functionality that is present in MS-SQL that is only in MS-SQL, like the reporting SP's.
Easy enough to pull an interface out of the ArachnodeDAO, but a lot more work to make it truly portable to another RDBMS.
Thanks!Mike
For best service when you require assistance:
An open source .NET web crawler written in C# using SQL 2005/2008.
Twitter: http://twitter.com/arachnode_net
arachnode.net provides custom crawling and contracting resources. Please ask.
C# crawler, C# web crawler, C# site crawler
Hello, 1/ Data validation is a problem of developer who impelment your interface,2/ Yea - this is a problem of developer too3/ I dont know how it works, but this i a problem of developer too
In summary, you give an elastic interface, with pre-built implementation of mssql. Developer who want to implement other RDMS take care about implement all methods which he needs to.