Storage Provider Configuration

Configuring a storage provider

Binner can support storing your part information using different database providers. By default, Binner will use the Binner custom binary file storage provider however you can also use SqlServer or any other supported provider.

Storage Providers

Binner

A custom binary database format that is persisted on your local file system but loaded in memory for very fast application usage. Changes to your inventory will save automatically to the file system, and you can choose where to store the database file. The disadvantage to using this format is you cannot edit any of the data directly without using the application, or use standard SQL queries against your data.

// appsettings.json
"StorageProviderConfiguration": {
    "Provider": "Binner",
    "ProviderConfiguration": {
      "Filename": "C:\\Binner\\binner.db"
    }
  },

SqlServer

Uses SQL Server to store your inventory data. If the database does not exist it will be created automatically. This provider is advantageous if you wish to integrate it with another application or manipulate the data outside of the application. Currently the following tables will be created: OAuthCredentials, Parts, PartTypes, Projects.

// appsettings.json
"StorageProviderConfiguration": {
    "Provider": "SqlServer",
    "ProviderConfiguration": {
      "ConnectionString": "Server=localhost;Database=Binner;Trusted_Connection=True;"
    }
  },

Other providers

We plan to build providers for MySQL, and Postgresql in the near future. PR's are welcome :)