Sorry, perhaps I wasn't clear:
It isn't the error that I am worried about, it is more that rawQuery
isn't documented as throwing a particular exception.
I can read my logcat and see plain as day that I had a syntax error in
my function.
I am trying to prevent something stupid like putting:
try{
rawQuery()
}catch(<b>Exception e</b>){
something bad happened to get here
}
instead it would be nice to catch the correct Exception in the first
place.
On Oct 27, 4:56 pm, DanH <danhi...@ieee.org> wrote:
> Thew SQLiteException generally contains some very useful text. Might
> be worthwhile telling us what it was.
>
> On Oct 27, 6:40 pm, swgillan <swgil...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hello,
>
> > I got an SQLiteException when executing a rawQuery() function. I
> > checked the API on this, and noticed that it is not documented that
> > rawQuery would throw this (otherwise I would have put try/catch for
> > this). Is this just something that was missed or is there something
> > else in the documentation I need to be reading in regards handling to
> > handling SQLite syntax errors?
>
> > Thank you,
>
> > Steven Gillan
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
