![]()
PRs which are solely about whitespace changes are ignored.It therefore has to be of high quality and changes made to the repository will live on forever so they aren't accepted without review. #Massive password repository codeThis is nothing personal, and to many of you these rules might sound rigid, but this repository isn't a playground for newbies: the code is used by many people and they depend on it. If you want to add new features to Massive or have a fix for a bug, that's great! There are some rules however and if you don't meet them, I won't merge your code, no matter how long you've worked on it. #Massive password repository how toThey can also be used as an example how to get started. #Massive password repository seriesIn v1.0 there were no tests but in v2.0 we properly implemented a series of tests to see whether things indeed work the way they do. In v1.0 code which was effectively the same among all supported databases was copy/pasted, in v2.0 Massive uses partial classes and shares as much code as possible among all supported databases. SQLite's ADO.NET provider does support async using specific types but Massive doesn't support these. ODP.NET (Oracle) doesn't support async under the hood so using the Async API with Oracle will still use synchronous data-access under the hood (through the default DbCommand fall back code). Full Async is supported by the ADO.NET providers of SQL Server and Npgsql (3.x). Not all supported databases support asynchronous data-access under the hood, but the Massive API at least allows you to work with the code asynchronously. What's new in v2.0īesides some changes as documented in the What's new in v2.0, the following features / additions are new: In general the breaking changes will be minor, if any. If you're using v1.0 currently and want to migrate to v2.0, please take a look at What's new in v2.0 page for more details about whether you'll run into the changes made. If you want to use the Devart driver, please change the value in property DbProviderFactoryName in the file around line 280 to. #Massive password repository driverHowever the free version of the Devart driver can be used in closed source development subject to some restrictions. At the time of writing the free version of the Oracle/MySQL driver must not be used in closed source development, though it can be used in many open source contexts. MySQL: Massive works with the Oracle/MySQL ADO.NET Driver ( ) and with the Devart dotConnect for MySQL driver ( ).Please read the official documentation on that provider to get started. SQLite: Massive uses the official SQLite.This installer will add the required DbProviderFactory reference and will add the npgsql dll to the gac. The Npgsql distribution contains an installer, offered at the If you want to use the Managed provider, please change the value in property DbProviderFactoryName in the file around line 297 to. By default Massive uses the latter, using the factory name. #Massive password repository fullThe installer for ODP.NET v12c installs both a full managed ADO.NET provider and a wrapper around its Java based Client Level Interface (CLI). The following ADO.NET providers are supported out of the box. This requires that the ADO.NET provider has been setup properly so. The ADO.NET provider is obtained through. It does have an indirect dependency, namely on the ADO.NET provider of the database used. Massive has no external direct dependencies, just get the code, compile it with your project and enjoy. If you need to use more than one database in your project, you have to change the namespace of the files and use per database a version of the Massive.Shared.* files. NET 4.5 or higher.ĭue to its design, all files share the same namespace.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |