I'm running into a minor problem integrating Rhino-ETL into my existing environment. My existing applications use the DbProviderFactories facility in System.Data.Common which was introduced in 2.0. Connection strings are defined at various levels in my system with some being defined at the machine level. Rhino-Etl uses the providerName attribute of a connection string to store the fully qualified type name of a connection class rather than a provider factory invariant.
Would you be open to a patch which addresses this issue? Additionally I have convention classes which handle the 'Merge Into' statement for SqlServer and the 'Insert or Replace into' statement in SQLite. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
