MySQL tinyint, bit and binary

jpardoe · Post by **jpardoe** » 31 Oct 2010, 10:48

I have data stored in a MySQL database which is being retrieved by DBManager.

It is working properly, however, with any data stored as type tinyint, bit or binary, the server outputs:

>>>> SKIPPING rowname -> -7

Why does this happen? How can I avoid the problem?

bart4president.com · Post by **bart4president.com** » 01 Nov 2010, 22:31

hmm.. best guess is perhaps its a datatype problem?

Perhaps cast the db data as a byte instead of a tinyint etc?

I am just speculating FYI.

jpardoe · Post by **jpardoe** » 02 Nov 2010, 05:45

Thanks for your suggestion but I don't think MySQL supports a byte data type.

I'd have thought a BIT would work though...it's only 1/8th of a byte lol.

bart4president.com · Post by **bart4president.com** » 02 Nov 2010, 19:38

Oh true.. i meant data coming in to your extension from a DB. Perhaps you need to type cast it.

jpardoe · Post by **jpardoe** » 03 Nov 2010, 04:11

The problem is, it's skipping unknown types before I get access to the data (it seems to be coming from dbManager.executeQuery()).

bart4president.com · Post by **bart4president.com** » 03 Nov 2010, 04:21

Yea i had pulled data from my DB and a BIG INT was viewed as a long in java so there might need some kind of unique resObj.get...

Fraggle · Post by **Fraggle** » 18 Apr 2011, 12:38

Same issue here using 2XRC2, tinyint fields are "SKIPPING".
Any idea how to fix it / when it will be fixed?

Post by **Lapo** » 20 Apr 2011, 11:02

We'll take a look. The bit type however is not supported.
Thanks for reporting

ericheimburg · Post by **ericheimburg** » 29 May 2011, 02:36

Any status on this? The "tinyint" type is supposed to be supported according to your help, but it just generates the ">>>> SKIPPING" message as reported by others.

(And the debugging spew is itself a minor bug, because that line of output is not being sent via a logger, it's just being printed to stdout!)

Is this bug (and the several other serious IDBManager bugs) going to be hot-fixed soon, or should we simply give up on using the IDBManager for our current generation of projects?

Thanks!

P.S. - one more IDBManager bug that I haven't seen reported yet: if a column is null, it is completely omitted from the results. According to the documentation, it should be included in the SFSObject, and be null.

Post by **Lapo** » 29 May 2011, 14:32

Coming in the next release, very soon.
Stay tuned.