Ignite.NET 2.3.0
I'm pulling data from another DB and loading into Ignite node started under
.NET Core console app. After converting the datarows into binary objects and
putting them into the cache, I both do a count as well as debug and see the
objects in the cache with the correct data.
I try p
I have a table defined as such and created via passing to an ODBC Connection:
CREATE TABLE IF NOT EXISTS TestTable (RecId varchar PRIMARY KEY, RecValue
DECIMAL(4,2))
WITH "template=replicated, cache_name=TestTable_Cache";
I then do an ODBC insert:
INSERT INTO TestTable (RecId, RecValue) VALUES
(Context - working in C#)
Vanilla single node cluster, no persistence (yet).
I executed a DDL statement via ODBC (CREATE TABLE BLAH (RecID varchar
PRIMARY KEY, Value1 varchar))
I see a cache was created via the web console (SQL_PUBLIC_BLAH).
I executed an Insert via ODBC (INSERT INTO BLAH (Rec
Igor Sapego-2 wrote
> You get "Table exists" error, because table is successfully
> created by the previous query. Error "Failed to find query
> with ID:[xx]" generated when ODBC statement is closed
> after execution of query that produced empty result set.
That makes sense, but I wouldn't expect
For what it's worth, a little more poking - the create table sql included the
option from the example in the docs...
CREATE TABLE IF NOT EXISTS TestTable [blah blah blah]
This was used over and over again to test with, always with the same
response (Failed to find query). To see if maybe the opt
Igor Sapego-2 wrote
> You used ODBC through C# to create table with CREATE TABLE
> command, right? If this is the case, then this is a known issue [1] for
> Ignite 2.3, which, I assume you are using. The issue already fixed
> and the patch was merged to master. As a workaround, you may try
> using
This should be super simple...
Started 2 nodes from the command line, they saw each other and now show
servers=2. Completely default configuration.
Installed the ODBC Driver and set up a DSN.
Started a C# app to open a connection and issue a create table sql
statement.
It fails with "Failed to
Just started playing with ignite, trying to put it thru its paces. After
successfully starting a cluster node, I started the web agent and headed out
to the gridgrain web console host and could see the agent talking to the
host. Awesome.
Next step was to look at integrating with an existing databa
