Log to database ORM DBISAM 4 error

Home Forums kbmMW Log to database ORM DBISAM 4 error

Viewing 4 reply threads
  • Author
    Posts
    • #55097
      jet2050
      Participant

      Hello!

      I’m trying to use the logging functionality of kbmMW Enterprise to an Elevate  DBISAM 4 database.

      I have tried using the following rewriters without success.

      • GenericAnsi2003SQL
      • GenericAnsi92SQL
      • MSSQL

      I get the following errores

      DBISAM Engine Error #11949 SQL parsing error – Expected end of statement but instead found 1 in SELECT SQL statement at line 1

      After that i get

      Data type rewrite not supported for field type:Memo

      This is the definition of TMyLog

      [kbmMW_Table(‘name:myLog’)]
      TMyLog= class
      private
      FID:kbmMWNullable<string>;

      FTime:TkbmMWDateTime;
      FInfo:kbmMWNullable<string>;
      FComments:kbmMWNullable<string>;

      public
      [kbmMW_Field(‘name:id, primary:true, generator:shortGUID’,ftString,40)]
      property ID:kbmMWNullable<string> read FID write FID;

      [kbmMW_Field(‘name:time’,ftDateTime)]
      [kbmMW_NotNull]
      property Time:TkbmMWDateTime read FTime write FTime;

      [kbmMW_Field(‘name:info’,ftMemo)]
      property Info:kbmMWNullable<string> read FInfo write FInfo;

      [kbmMW_Field(‘name:comments’,ftMemo)]
      property Comments:kbmMWNullable<string> read FComments write FComments;
      end;

      Am I doing something wrong?

      Thanks for the help

      Regards

      Job Espejel
      <div id=”kpm-root” class=”kpm_LTR notranslate” translate=”no”></div>

    • #55109
      mrluigi2017
      Participant

      Could you log the SQL statement? I use Devart and they have a monitor tools which shows you all the SQL which is sent to the user. If not you could maybe use the kbmmw log function:

      kbmMWDebugLevel := mwdlAll;
      kbmMWDebugWhere := mwddDebug;
      kbmMWDebugTypes := [mwdtDBQuery];

      It logs to the IDE messages window.

    • #55125
      kimbomadsen
      Keymaster

      I know there has been reported an issue resolving back to DBISAM4 databases from kbmMW.

      The issue seems to be some versions of DBISAM v4 not liking double quoting the table name in the generated SQL statements.

      The DBISAM v4 manuals indicate that double quoting a table name should be valid, but it seems not to work always.

      For that reason, you can change TableNameQuote to a single quote or #0 or set QuoteTableName to false in the TkbmMWDBISAM4MetaData instance you use, then try out if it works as expected.

    • #55144
      Babis Michael
      Participant

      The same problem exists ElevateDB!

    • #55156
      kimbomadsen
      Keymaster

      But it is strange that it is an issue since page 14 of this document clearly states that tablenames should be double quoted.

      Click to access dbisam4rscppxe.pdf

       

       

Viewing 4 reply threads
  • You must be logged in to reply to this topic.