Products

Home Forums eaDocX queries Cant generate EADoc for models in mySQL repository

Home Forums eaDocX queries Cant generate EADoc for models in mySQL repository

Viewing 15 posts - 16 through 30 (of 30 total)
  • Author
    Posts
  • #6873
    eadocX Support
    Participant

    I’m as baffled as you.
    I will add another fix, to change the table name to lower-case for mySQL, as my local mySQL implementation doesn’t seem to care whether its upper- or loer-case. This is all very odd, as eaDocX submits this SQL to EA, who sends it right off to the DBMS. eadocX uses the same style of SQL – upper-case table names – for all the direct-to-DBMS calls, so it’s surprising that just this one to t_objectproperties causes problems.

    #6874
    rick sipin
    Participant

    Thanks! I’m sure the issue is in the bowels of the ODBC driver. Having worked with a number of those over the years, there’s just some which are more ‘flaky’ than others. I suspect that this fix will be welcomed by a number of MySQL users. For anyone interested, the versions I listed in the first post on this thread have been really stable for us in both EA and eaDocX. We have quite a large corporate model repository with over 10,000 object in it.

    #6875
    eadocX Support
    Participant

    OK Rick – done that. It’s on the website as 3.3.10.5. See if that does the trick.

    #6876
    rick sipin
    Participant

    OK, well that new build didn’t work. The tablename isn’t being completely reported in the error dialog – same add attribute operation as noted before – t_objectproperties shows up in the error dialog as Table ‘myschema.T_OBJECT’ doesn’t exist. Should note that the 3.3.10.5 build shows as a trial vs. a complete install like the 10.4 build did.

    Want to give it another shot?

    #6877
    Raelene Rushing
    Participant

    Attached is a sample file where we were getting Tobject table error….sorry for the delay…

    #6878
    eadocX Support
    Participant

    Ah – thats makes more sense: it’s looking for T_OBJECT in a DB which contains only t_object, so it’s not just the t_objectproperties table which needs to be lower-case – it’s all of them.
    This is a much more disruptive change: I need to change ALL the places where I issue direct SQL, to have lower-case table names, which is a load of calls, all of which need to be regression tested, and some of them only get used in some obscure situations.
    As I can’t reproduce this on a local mySQL DBMS, I can’t then test it for you.
    Do you think it’s become case-sensitive due to being implemented on a remote Linux machine? Have you tried with a local Windows mySQL?
    Is this the kind of thing which Linux machines tend to do?
    Any chance of you trying a schema change, to make a couple of tables upper-case, and check that EA doesn’t mind?

    #6879
    rick sipin
    Participant

    I can do each of those, it’ll just take some time. As our repository has over 10K objects in it, I’ll have to do it on another instance, and involve our support staff. I’ll see if I can get different behavior on a windows instance. I’ll run some tests and get back to you on what we find.

    Thanks again for the excellent responses. Hopefully we’ll track this down to a path that works for us. I’ll stick with the 3.3.10.4 build as it at least fixes the mixed case table name, which probably would remain an issue.
    -Rick

    #6880
    eadocX Support
    Participant

    Thanks Rick – I’ve backed-out v3.3.10.5, so current version is still 3.3.10.4

    #6881
    Raelene Rushing
    Participant

    sorry…renamed. from .xml to .txt…so I can upload

    #6882
    rick sipin
    Participant

    So here’s the result of a test that I ran. Again, here’s the versions we’re running which we’ve had decent luck with most eaDocX features using a MySQL repository:
    MySQL 5.0.77 redhat-linux-gnu(x86_64)
    MySQL ODBC 5.1 Driver
    eaDocX 3.3.10.2 Professional Edition (updated recently to 3.3.10.4)
    EA Version 10.0.1004

    We’re running win7 – 32 bit clients and a few XP clients.

    I had our MySQL repository cloned, and renamed all of the tables, and updated the tablenames in the usystables table to all be uppercase (i.e. T_OBJECT). Unfortunately, something in EA immediately took issue to this, and I could not open the repository, and was getting all sorts of errors where EA is expecting (through SQL pass-through I’m sure) lower case table names. At this point, I may try adjusting just the few places where we’re seeing eaDocX operation raise an error because of the expectation of an uppercase table name (as I mentioned in earlier post), but we may end up moving from mySql anyway. If you want most of the documentation features and EA to work using a MySQL repository, I’d still recommend the configuration we’ve had running for about 3 years now.

    • This reply was modified 10 years, 8 months ago by rick sipin. Reason: version correction
    #6884

    Just ran into the same problem running MySQL 5.5.27 on a Linux server.

    Any news on this?

    RGDS
    Tage

    #6885
    eadocX Support
    Participant

    Sorry about this. Our plan is to fix in v3.4, which should have a beta available in a couple of weeks. Sorry for the delay, be we’re now also regression testing with EA V11 as well….

    #10386
    Marie Due
    Participant

    Hi dear support team
    we are using postgreqsl for our model and when we want to use modelexpert dashboard we get the following error from dotnet framework
    System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3710.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
    —————————————-
    System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3770.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
    —————————————-

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging=”true” />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    #10387
    Marie Due
    Participant

    Hi dear support team
    we are using postgreqsl for our model and when we want to use modelexpert dashboard we get the following error from dotnet framework
    System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3710.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
    —————————————-
    System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3770.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
    —————————————-

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging=”true” />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ArgumentNullException: Value cannot be null.
    Parameter name: key
    at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
    at Model_Expert.EARepository.diagramElementTypeCounts(EAPackage aPackage)
    at Model_Expert.cntlAnalysisDashboard.fillDiagramsTable()
    at Model_Expert.cntlAnalysisDashboard.openOnRefModel(MXReferenceModel aRefModel, EAPackage sourcePackage, WorkingSet ws)
    at Model_Expert.cntlEADockableDashboard.bwAnalyser_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
    at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
    at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)

    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3860.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    —————————————-
    Model_Expert
    Assembly Version: 2.2.2.1
    Win32 Version: 2.2.2.1
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Model_Expert.DLL
    —————————————-
    Interop.EA
    Assembly Version: 2.10.238.1
    Win32 Version: 2.10.238.1
    CodeBase: file:///C:/Program%20Files%20(x86)/Sparx%20Systems/EA/Interop.EA.DLL
    —————————————-
    eaDocXAddIn
    Assembly Version: 5.0.5.3
    Win32 Version: 5.0.5.3
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX%20Ltd/eaDocX/eaDocXAddIn.DLL
    —————————————-
    LogicNP.CryptoLicensing
    Assembly Version: 6.0.0.0
    Win32 Version: 6.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX%20Ltd/eaDocX/LogicNP.CryptoLicensing.DLL
    —————————————-
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3830.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    —————————————-
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3640.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    —————————————-
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    —————————————-
    Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
    —————————————-
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3830.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    —————————————-
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3630.0 built by: NET472REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    —————————————-
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    —————————————-
    Telerik.WinControls.UI
    Assembly Version: 2021.1.326.40
    Win32 Version: 2021.1.326.40
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Telerik.WinControls.UI.DLL
    —————————————-
    Telerik.WinControls
    Assembly Version: 2021.1.326.40
    Win32 Version: 2021.1.326.40
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Telerik.WinControls.DLL
    —————————————-
    TelerikCommon
    Assembly Version: 2021.1.326.40
    Win32 Version: 2021.1.326.40
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/TelerikCommon.DLL
    —————————————-
    Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    —————————————-
    Telerik.WinControls.ChartView
    Assembly Version: 2021.1.326.40
    Win32 Version: 2021.1.326.40
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Telerik.WinControls.ChartView.DLL
    —————————————-
    Gma.CodeCloud.Controls
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Gma.CodeCloud.Controls.DLL
    —————————————-
    Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    —————————————-
    System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
    —————————————-
    CustomMarshalers
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3190.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/CustomMarshalers/v4.0_4.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
    —————————————-
    Telerik.WinControls.GridView
    Assembly Version: 2021.1.326.40
    Win32 Version: 2021.1.326.40
    CodeBase: file:///C:/Program%20Files%20(x86)/eaDocX/Model%20Expert/Telerik.WinControls.GridView.DLL
    —————————————-
    System.Data
    Assembly Version: 4.0.0.0

    #10420
    Ian Mitchell
    Keymaster

    Hi – please you submit this to the Model Expert forum

Viewing 15 posts - 16 through 30 (of 30 total)
  • You must be logged in to reply to this topic.

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download