Details

    • Type: Bug
    • Status: Stalled
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.0.17
    • Fix Version/s: 10.0
    • Labels:
    • Environment:
      Windows Server 2008 64-bit, MariaDB 10.0.17 .ZIP (portable)

      Description

      After upgrading (past upgrades all no problem) from 10.0.15 to 10.0.17 several "CREATE table" with ENGINE=CONNECT table_type=XML fail.
      This happens with XML files that have ":" in the attributes, like for example: <Test xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"></Test>
      When trying to use option_list='xmlsup=LIBXML2' one gets SQL Error (1105): libxml2 not supported by this version.
      If option_list='xmlsup=DOMDOC' then SQL Error (1296): Got error 174 'Loading of /test.xml failed' from CONNECT.
      On version 10.0.15 was working OK without xmlsup option definition.
      Now even copying over all the .exe, etc files to previous version (but maitaining the data) keeps the same problem.
      Strangely all versions now report in the boot log: CONNECT: Version 1.03.0006 Jan 25 2015 07:43:28 while the MariaDB website says the latest version as of today is 1.03.0005 !
      This blocked all my projects. Hope a good soul can check this issue.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            <serg> dbart: now connect engine doesn't link, it cannot find many (or all) xml* symbols

            ....

            <serg> he created c:\libxml2 and c:\libxml2_win64
            <serg> I've renamed the first one to c:\libxml2_win32
            <serg> so neither is used currently

            Show
            elenst Elena Stepanova added a comment - <serg> dbart: now connect engine doesn't link, it cannot find many (or all) xml* symbols .... <serg> he created c:\libxml2 and c:\libxml2_win64 <serg> I've renamed the first one to c:\libxml2_win32 <serg> so neither is used currently
            Hide
            elenst Elena Stepanova added a comment -

            Novitsky,
            After 10.0.20 release, could you maybe give advice on how to handle it properly?

            Show
            elenst Elena Stepanova added a comment - Novitsky , After 10.0.20 release, could you maybe give advice on how to handle it properly?
            Hide
            Lawrin Novitsky added a comment -

            I looked into both connect's CMakeList.txt and FindLibXml2.cmake - it will find libxml2 only in c:|d:/libxml or c:/libxml2
            But we can hint cmake like
            cmake -DCONNECT_WITH_LIBXML2:BOOL=TRUE -DPC_LIBXML_LIBDIR=c:/libxml2_win32/lib -DPC_LIBXML_INCLUDEDIR=c:/libxml2_win32/include .
            the other way would be to add path to specific cmake (env)variables, or to PATH LIB/INCLUDE
            btw the dll itself is in bin subdirectory, just in case you will need to test it after build.

            Show
            Lawrin Novitsky added a comment - I looked into both connect's CMakeList.txt and FindLibXml2.cmake - it will find libxml2 only in c:|d:/libxml or c:/libxml2 But we can hint cmake like cmake -DCONNECT_WITH_LIBXML2:BOOL=TRUE -DPC_LIBXML_LIBDIR=c:/libxml2_win32/lib -DPC_LIBXML_INCLUDEDIR=c:/libxml2_win32/include . the other way would be to add path to specific cmake (env)variables, or to PATH LIB/INCLUDE btw the dll itself is in bin subdirectory, just in case you will need to test it after build.
            Hide
            bertrandop Olivier Bertrand added a comment -

            Did someone succeeded to get a 64bit version of libxml2 on Windows?
            Apparently a 32bit lib cannot be used by a 64bit version of MariaDB causing link edit errors.

            I have downloaded the libxml2-2.9.2-win32-x86_64.7z from xmlsoft.org/sources/win32/64bits/ and expanded it in c:\libxml2 but unsuccessfully. Firstly because the directory layout is different (it makes a subdirectory libxml2-2.9.2-win32-x86_64 in c:/libxl2) but this can be manually corrected. Secondly because the lib subdirectory does not contain the required libxml2.lib but libxml2.a as if it were containing a Linux version .

            Show
            bertrandop Olivier Bertrand added a comment - Did someone succeeded to get a 64bit version of libxml2 on Windows? Apparently a 32bit lib cannot be used by a 64bit version of MariaDB causing link edit errors. I have downloaded the libxml2-2.9.2-win32-x86_64.7z from xmlsoft.org/sources/win32/64bits/ and expanded it in c:\libxml2 but unsuccessfully. Firstly because the directory layout is different (it makes a subdirectory libxml2-2.9.2-win32-x86_64 in c:/libxl2) but this can be manually corrected. Secondly because the lib subdirectory does not contain the required libxml2.lib but libxml2.a as if it were containing a Linux version .
            Hide
            Lawrin Novitsky added a comment -

            I can confirm that. the dll can be find in the bin subdir as well, though it is named libxm2-2.dll for unknown reason. Can be renamed, of course. But where is no import library for dll in the lib. There is libxml2.dll.a - there is such file in 32bit distribution, I guess that is strangely named static library

            Show
            Lawrin Novitsky added a comment - I can confirm that. the dll can be find in the bin subdir as well, though it is named libxm2-2.dll for unknown reason. Can be renamed, of course. But where is no import library for dll in the lib. There is libxml2.dll.a - there is such file in 32bit distribution, I guess that is strangely named static library

              People

              • Assignee:
                dbart Daniel Bartholomew
                Reporter:
                jgfs Joao Ferreira
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours
                  2h