Theming of ODBC database layer errors

[andrewd]

I've got an point layer coming from an ODBC dataconnection. When trying to Theme the point symbol, I get all sorts of errors - eventually Maestro just froze.

If I just test out various fields, I get problems with a number field (Single type) - I get a message from Maestro saying "Unable to read from the selected column: Unknown type: System.Single". If I try a text field (255 long), I get a total freeze. If I try another text field (the one that I actually want, in this case) that is 50 long, I get the attached screen cap. So, that leaves no field types that actually work.

These all work in MG Studio - I can theme this layer properly from there...

[andrewd]

Screen cap

[jng]

Retargeting for 3.0 If you're a 3.0 tester, see if this issue still applies and/or relevant

[andrewd]

The problem still exists in 3.0, except with a slight improvement - my 50 char string field works. The 255 one still freezes Maestro, and the Singles still throw the same error.

[jng]

What is the underlying ODBC data source (MS Access?). How are these columns defined? (the 255 char one and the System.Single one). Trying to create a test database and want to make sure FDO is not re-interpreting these column data types.

[andrewd]

MS Access - right. The columns in question are:

data type = "number", field size = "single" data type = "text", field size = "255"

The singles never work. I always get that same error. Interestingly, just now, when I was trying to get a refresher on the problem, I tried one of the 255 char fields first, and it worked. Now, that field had no data in it, so I got "no non-null values" message - fair enough. It could be that Maestro just freezes after a while while in the Theme Creator, and because my 255 text fields are at the end, it just happens to freeze when I get to them.

I can't make it freeze by doing the exact same thing each time, but I can make it freeze everytime. It seems as if I just go into the Theme Creator and keep flipping between different fields (there are about 15 in my table), it will eventually freeze up - usually on a text field (if not always).

[jng]

Please re-test against 3.0 beta 1

[andrewd]

screen cap of "edit schema" error

[andrewd]

I've just uploaded a new screenshot. I get this error when I try to edit any of my datasource's schema. As soon as I press the "edit schema" button, I get this error. So I can't test this...at least not without making a new datasource.

[jng]

It's failing to parse the configuration document to an object-oriented form.

Can you click Edit Configuration Document at the bottom of the editor and attach a file containing this XML content? Trac screws up formatting if you paste the XML content inline. I want to see the XML content that Maestro's failing to parse.

[andrewd]

configuration doc

[andrewd]

Still not fixed in Beta 2. By that, I mean I still get an error when trying to edit the schema for an existing datasource - and of course, that means I can't test this specific bug either. Should I make a new ticket? I'm wondering if this just got missed because this schema issue is inside of this ticket...This schema thing is a blocker, in my books.

[jng]

I'm afraid I have no choice but to ask that you attach a package of the data containing this problematic ODBC feature source and any layers referencing it. If the feature source is to an externally referenced file, I'll need a copy of that too.

If you can't attach it due to size/confidentiality/etc, you can email the files to me.

[andrewd]

It's happening on all of my datasources, not just one...which is why it's such a blocker for me. I also just tried making a new one and can't make a single one. I've got 16 different DSNs to pick from, but in every case when I click "edit schema" I get this error. These datasources are mostly MSAccess, but a few are SQL Server - like I said, none are working in v3 (but all work fine in v2). I take it you don't have this problem? I'm running Windows 7 x64 on my machine - and my server (where the DSNs live) is Windows Server 2008 x64 (though those DSNs are 32bit).

[andrewd]

Do you need anything more from me on this, to get the ball rolling on this? I could possibly send you a datasource, but like I said, this is happening even if I make a new one...

[jng]

Well you said from the original description that the theming works MGStudio where it fails in Maestro. Can you package up one such feature source?

[andrewd]

I could - but now I'm talking about this other (more serious) bug which prevents me from even making an odbc datasource....which prevents me from testing this specific ticket.

[jng]

Ok, lets backtrack a bit here. It is becoming clear we're talking about 2 separate things here.

File a separate ticket on this inability to create an ODBC feature source and we'll carry on the relevant discussion there. If you can attach to that ticket an access database which when accessed as a ODBC DSN reproduces the problem you describe, that would be really helpful

[andrewd]

Ya, I'd suggested creating a new ticket a couple of days ago - must've gotten missed. The new ticket can be found here: ​http://trac.osgeo.org/mapguide/ticket/1640

Once that's addressed, I can see if this ticket has been taken care of.

[jng]

Now that #1640 is effectively fixed, does the original issue in this ticket still occur?

[jng]

Did the release of Maestro 3.1 solve this issue for you?

[andrewd]

See ticket #1477. Based on that, I'm going to guess that this is still not working...

[jng]

Fixed with use of UNIQUE() aggregate function to fetch distinct themeable values in r6202