4

In the documentation for DatabaseUtils.concatenateWhere(...) it is stated that it is supported from API level 11+ (HONEYCOMB). However, while testing compatibility on various devices, that on my Droid X running Cyanogenmod 7 nightly build 98 (based on gingerbread 2.3.5), the method call not only does not cause a crash, but works as expected.

Is this some inconsistency with my custom ROM, or can anyone else reproduce this functionality on another device that is running Gingerbread or lower? Could this be an error in the SDK documentation?

Community
  • 1
  • 1
Jon Willis
  • 6,993
  • 4
  • 43
  • 51

2 Answers2

5

It looks like an error in the documentation.

GrepCode shows that the method exists in Android 2.3.4_r1.

In fact, the method exists in all versions including 1.5_r4.

David Snabel-Caunt
  • 57,804
  • 13
  • 114
  • 132
  • "In fact, the method exists in all versions including 1.5_r4." Does that mean it is safe to use it? What about devices with the first revisions of the corresponding SDKs? – Jon Willis Sep 21 '11 at 15:52
  • Is it safe to use? It appears so - I would test on a few different API levels, but it's just performing a simple operation on two Strings. As for earlier revisions, I'm not exactly sure how these work, but I think these are only required to compile your app - the operating system itself does not have revisions. – David Snabel-Caunt Sep 21 '11 at 16:13
0

Well, Android 2.3.5 was released after Honeycomb. I don't find it unreasonable that Google might have implemented certain APIs from Honeycomb to help fight fragmentation. I wouldn't count on it working in other versions of Gingerbread though, without thorough testing.

Nick
  • 6,900
  • 5
  • 45
  • 66