Connecting to mariadb

[jshand2010]

I am having trouble trying to get this code to work...  can someone let me know where i'm going wrong?  i get the error about a transaction not being set.

[mangakissa]

What error?
Piece of code instead of whole project?

[jshand2010]

just look into the provars.pas file.  this is where the error is.  it happens as i load loadlogintb procedure.  i presume the loaddb; code is correct to get things started

[Thaddy]

Try mysql57conn -->> mysql56conn
That one is still MariaDb compatible.

Note we would probably need to start a new component for MariaDb. It is diverging.
I did not test this yet, but just try first.

[jshand2010]

thanks thaddy, i forgot about that technicality.  i will test it and let you know

[jshand2010]

here is the code snippet:  it still doesn't work with mysql56conn:

a:=0;
  clearul(a);
  cleartl;

  loaddb;

  try
    if (conn.Connected=true) then begin
      query.Close;
      query.SQL.Clear;
      query.SQL.Add('select uname, pword from userlogintb;');
      query.ExecSQL;
      query.Last;
    end;
  except
    on err: ESQLDatabaseError do begin
      ShowMessage(err.Message);
      ShowMessage(err.UnitName);
    end;
  end;   

[rvk]

You set the database in the transaction.

But you should also set the transaction in the connection and the sqlquery. You forgot to do that.

[mangakissa]

Query.ExecSQL doesn't get a dataset for you. So there are no records to check.

[Thaddy]

Query.ExecSQL doesn't get a dataset for you. So there are no records to check.

Why does it is name says QueryXXX then? A query is supposed to return a dataset.... Is this true? Then it's a bug. If only poor language choice.

Query means: I am asking and would like to have (an) answer(s). Usually you get one at least....

[rvk]

Query.ExecSQL doesn't get a dataset for you. So there are no records to check.

Why does it is name says QueryXXX then? A query is supposed to return a dataset.... Is this true? Then it's a bug. If only poor language choice.
 I am asking and would like to have (an) answer(s). Usually you get one at least....

Although this is a TSQLQuery component, the ExecSQL does NOT return a dataset. It just executes a statement. So consider the ExecSQL a "helper" function which you use to execute a statement when you don't need to have a result-set. You could also use a separate TSQLScript or even use the .ExecuteDirect() from the connection-component instead.

From the manual:
http://www.freepascal.org/docs-html/fcl/sqldb/tcustomsqlquery.execsql.html

ExecSQL will execute the statement in TSQLQuery.SQL, preparing the statement if necessary. It cannot be used to get results from the database (such as returned by a SELECT statement): for this, the Open method must be used.

This is a well known fact of the .ExecSQL() function.

[mangakissa]

Create an example for check login. It's not the best solution, but it works.

[Thaddy]

[Although this is a TSQLQuery component, the ExecSQL does NOT return a dataset. It just executes a statement. So consider the ExecSQL a "helper" function which you use to execute a statement when you don't need to have a result-set. You could also use a separate TSQLScript or even use the .ExecuteDirect() from the connection-component instead.

From the manual:
http://www.freepascal.org/docs-html/fcl/sqldb/tcustomsqlquery.execsql.html

ExecSQL will execute the statement in TSQLQuery.SQL, preparing the statement if necessary. It cannot be used to get results from the database (such as returned by a SELECT statement): for this, the Open method must be used.

This is a well known fact of the .ExecSQL() function.

So I was right (again). Semantics. Design error. Problem is that most people have no clue about software design.Introducing this functionality in the wrong place is moronic. It is wrong.  Go shopping for apples and bring back pears.

[mangakissa]

If this is a design error, all database frameworks are wrong designed. I can not tell you which framework gives a dataset back when using execSQL.

[mangakissa]

Create an example for check login. It's not the best solution, but it works.

Does it work?

[balazsszekely]

Most definitely not a design error, though I agree the query word can be misleading.