Dennis Cote wrote: > The following log shows that sqlite does indeed distinguish > between a text field and a blob with the same content. It also > shows you a workaround. You simply need to cast your fields to > blobs before you compare them to a variable that is bound to a > blob.
But I can't do that. I'm writing a language binding, not an application*, so changes to the query text are outside the realm of what I can play with. But the fact that it exists is actually really helpful, because I can just write it into the docs as a known gotcha without chucking my design entirely, and especially because it focuses my earlier question better: If [1] SQLite automatically casts between types as needed in most cases (e.g. real to/from string) and [2] the cast() syntax already works to convert between strings and blobs in the "obvious" way, then: why is the cast automatic for numberic values, but not for strings/blobs? Isn't that a non-orthogonality design flaw? Andy * ..er, well, I'm writing a language binding *and* an app at the moment. But I'm much more concerned about the problems with the bindings. As I mentioned earlier, I can already work around the issue by making sure all columns that will be queried with parameters are specified as blobs. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------