Mathematica Stack Exchange is a question and answer site for users of Mathematica. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm trying to figure out how these statements really work, and am having some trouble with the documentation (and the software!).

Using the example publishers database (Mathematica 8), the following works fine (as documented):


Now, there is no column ROYALTY in the TITLES table, so perhaps I should be able to write


But this results in the error

    cannot be converted to a value in an SQL statement.

So apparently either none or all of the entries in the columns list must themselves be lists. Is this right, or a bug, or what?

So assuming that this is correct, and all the columns must be lists in any multi-table inner join, how can I then apply a function such as COALESCE to the results to cast NULLs to zero? I tried {"TITLES","COALESCE(TITLE_ID,0) AS TITLE_ID"}, which failed because the string passed to the JDBC driver was TITLES.COALESCE(TITLE_ID,0) AS TITLE_ID, which is of course incorrect.

At the risk of asking too many questions in one question, let me add: I'm perfectly OK with simply returning the rows I want, with whatever NULLs may be in them. But can someone tell me the right way to turn all those NULLs to zeros once the result set is a Mathematica list?

share|improve this question
It does not sound like a bug to me. It wants to know what table each field belongs to even when there's no conflict, not necessary in all strains of SQL but not a very strange requirement for a multi-table query either. For more advanced queries you can turn to SQLExecute. To replace NULL, simply do list /. Null->0. – Pickett Aug 4 '13 at 9:52
@Anon Sure, but SQLSELECT[conn,{"TITLES","ROYSCHED"},{"TITLE","ROYALTY"}] works just fine --- and TITLE is a column only in TITLES, ROYALTY only in ROYSCHED. – rogerl Aug 5 '13 at 0:23
Then I guess it is as you say it is. You can report it as a bug I guess and they may tell you if it's a bug or not. – Pickett Aug 5 '13 at 7:15
up vote 3 down vote accepted

If you examine Information[SQLSelect] you'll see the various input patterns allowed for SQLSelect. It's quite long but the relevant parts are:




Indeed, it allows either strings, lists of strings, and lists of lists of strings (and of course SQLColumn). However, there is no pattern for a mixture of these inputs. Whether this is by design or caused by oversight I'm unable to tell, but since this is the exposed interface I wouldn't call the behavior you noticed a bug.

To enter your COALESCE function you could use raw SQL:

SQLExecute[conn, "
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.