Aerospike.Database.LINQPadDriver
2.0.5
See the version list below for details.
dotnet add package Aerospike.Database.LINQPadDriver --version 2.0.5
NuGet\Install-Package Aerospike.Database.LINQPadDriver -Version 2.0.5
<PackageReference Include="Aerospike.Database.LINQPadDriver" Version="2.0.5" />
paket add Aerospike.Database.LINQPadDriver --version 2.0.5
#r "nuget: Aerospike.Database.LINQPadDriver, 2.0.5"
// Install Aerospike.Database.LINQPadDriver as a Cake Addin #addin nuget:?package=Aerospike.Database.LINQPadDriver&version=2.0.5 // Install Aerospike.Database.LINQPadDriver as a Cake Tool #tool nuget:?package=Aerospike.Database.LINQPadDriver&version=2.0.5
Aerospike Database for LINQPad 7
Description
Aerospike for LINQPad 7 is a data context dynamic driver for querying and updating an Aerospike database. This driver can be used to explore an Aerospike data model, data mining, prototyping, testing, etc.
You can perform the following:
- query any Aerospike Set using any LINQ command.
- use the driver’s extension methods to perform operations like Aerospike Expression, CRUD operations, import/export, or execute an Aerospike User Defined Function (UDF) without understanding the underlying Aerospike API.
- use the Aerospike API to perform advance operations or just to test code segments used in your application.
The driver can dynamically detect the structure of records in Aerospike Sets resulting in an easy-to-understand view. The driver can also detect multiple data types for the same Aerospike Bin within a record. Below screenshot show how Aerospike Sets and Bins are represented in LinqPad:
The LINQPad connection pane will display the different Aerospike components in an hierarchical manner where namespace is under Aerospike cluster connection. Aerospike Sets are under namespaces and bins are under Sets. Below screenshot shows the relationship between these components:
Each component can be dragged-and-dropped onto the LINQPad Query pane to be executed by LINQPad. The execution behavior will depend on the component. For example, a Set or Secondary Index will present the records within that component. For other components, the properties are displayed. In all cases, you can always execute the driver’s extension methods. These extension methods, greatly simplify Aerospike API commands like Get, Put, Query, Operate, etc. plus, the ability to perform things like importing or exporting data. Of course, you can always use LINQ against Aerospike Sets or Secondary Indexes. Below is an example of some of the driver extensions:
Aerospike Namespace, Set, Records, Bins, and Secondary Indexes
The LINQPad connection pane will display the different Aerospike components in a hierarchical manner where namespace is under Aerospike cluster connection. Aerospike Sets are under namespaces and bins are under Sets. Below screenshot shows the relationship between these components:
Each component can be dragged-and-dropped onto the LINQPad Query pane to be executed by LINQPad. The execution behavior will depend on the component. For example, a Set or Secondary Index will present the records within that component. For other components, the properties are displayed. In all cases, you can always execute the driver’s extension methods and properties. These extensions, greatly simplify Aerospike API commands like Get, Put, Query, Operate, etc. plus, the ability to perform things like importing or exporting data. Below is an example of some of the driver extensions:
Aerospike Sets and records are very easy to use. The detected bins in a record are integrated into LINQPad and are treated as C# properties. As such, features like Intellisense and Autocompletion just work. You can also access bins within a record by using the bin name.
Since Aerospike is a schemaless database, a record can consist of varying number of bins, or a bin can have different data types between records. The driver can handle these conditions seamlessly. This is done using extension methods and implicit data conversion.
Implicit data conversion eliminates the need to test and cast a bin’s value so that it can be used directly in any operation. Below is an example that shows how implicit conversion works. The set, “graphDeviceNodeIdSet”, has a bin named “nodeID” that consists of two different data type values. Some records have a list value while others have a string value. This example uses the “where” clause which compares each record in the set looking for a numeric value of 367 or the value “a” in the list values.
User-Defined Functions (UDFs)
The driver supports the execution of UDFs by calling the Execute extension method. The Execute method will reflect the actual arguments used in the UDF. Below is an example:
Aerospike API
At anytime you can use the underlying Aerospike API directly or a combination of API or driver extension methods. Below is an example:
Prerequisites
Installation
NuGet
- Open LINQPad
- Click
Add Connection
Link. - Click button
View more drivers…
- Click radio button
Show all drivers
and typeAerospike
. - Install
Manual
Obtain the latest driver from the Driver
folder and download to your computer.
- Open LINQPad
- Click
Add Connection
Link. - Click button
View more drivers…
- Click button
Install driver from .LPX6 file…
and select downloaded lpx6 file.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net6.0-windows7.0 is compatible. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net7.0-windows7.0 is compatible. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp3.1 is compatible. |
-
.NETCoreApp 3.1
- Aerospike.Client (>= 5.3.1)
- LINQPad.Reference (>= 1.3.0)
- Newtonsoft.Json (>= 13.0.3)
-
net6.0-windows7.0
- Aerospike.Client (>= 5.3.1)
- LINQPad.Reference (>= 1.3.0)
- Newtonsoft.Json (>= 13.0.3)
-
net7.0-windows7.0
- Aerospike.Client (>= 5.3.1)
- LINQPad.Reference (>= 1.3.0)
- Newtonsoft.Json (>= 13.0.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated | |
---|---|---|---|
3.4.5 | 61 | 10/31/2024 | |
3.4.3 | 75 | 10/22/2024 | |
3.4.2 | 60 | 10/17/2024 | |
3.4.0 | 114 | 7/27/2024 | |
3.3.1 | 193 | 4/15/2024 | |
3.2.0 | 172 | 3/4/2024 | |
3.1.0 | 195 | 1/17/2024 | |
3.0.2 | 190 | 1/3/2024 | |
3.0.1 | 186 | 1/2/2024 | |
3.0.0 | 202 | 12/21/2023 | |
2.3.3.1 | 199 | 12/5/2023 | |
2.3.3 | 226 | 11/2/2023 | |
2.3.2 | 218 | 10/12/2023 | |
2.3.1 | 190 | 9/25/2023 | |
2.3.0 | 188 | 9/23/2023 | |
2.1.2 | 283 | 8/22/2023 | |
2.1.1 | 236 | 8/9/2023 | |
2.1.0 | 257 | 7/14/2023 | |
2.0.6 | 252 | 6/19/2023 | |
2.0.5.17 | 257 | 6/7/2023 | |
2.0.5.16 | 247 | 6/1/2023 | |
2.0.5.15 | 246 | 5/30/2023 | |
2.0.5.14 | 218 | 5/26/2023 | |
2.0.5.12 | 247 | 5/17/2023 | |
2.0.5.11 | 251 | 5/17/2023 | |
2.0.5.10 | 210 | 5/16/2023 | |
2.0.5.8 | 219 | 5/12/2023 | |
2.0.5.7 | 223 | 5/11/2023 | |
2.0.5.6 | 230 | 5/10/2023 | |
2.0.5.4 | 188 | 5/6/2023 | |
2.0.5.3 | 198 | 4/27/2023 | |
2.0.5.2 | 262 | 3/28/2023 | |
2.0.5.1 | 313 | 3/23/2023 | |
2.0.5 | 332 | 3/22/2023 |