RE: [sqlite] Let us make SQLite more powerful

2003-12-15 Thread Steve O'Hara
Here's my tuppence worth; I've been working with BASIS for donkeys years and it is one of the few RDBMS that fully supports multi-occurence fields. To search for a value in such a field you simply say SELECT LastName FROM Contacts WHERE Phones = "2064814442" This means search in any occura

RE: [sqlite] Let us make SQLite more powerful

2003-12-15 Thread Mrs. Brisby
All I was demonstrating was how to use a single field. It's obviously better to use a second table and build a relationship using JOIN. I don't see where "multi-occurrence" fields can do something that JOIN-ed relationships can't. SELECT LastName FROM Contacts JOIN Phones USING (phoneID) HAVING P

[sqlite] BLOB support and SQLite 3.0

2003-12-15 Thread D. Richard Hipp
Mrs. Brisby wrote: [...] I really would like to see user-defined "structures"- but I suspect this will have to wait for SQLite 3.0 or whenever we get non-null-terminating values... You can do that now. The (experimental) sqlite_bind() API available in 2.8.7 allows you to insert arbitrary binary da

Re: [sqlite] Let us make SQLite more powerful

2003-12-15 Thread Dennis Cote
>From: "Mrs. Brisby" <[EMAIL PROTECTED]> > > But it would make the engine more complex- for a direction that isn't > standard, ... All of the proposed changes are in fact part of the SQL:1999 standard. Since all the proposed changes are related to SQL data typing, they are fundamentally in contr

Re: [sqlite] BLOB support and SQLite 3.0

2003-12-15 Thread Mrs. Brisby
On Mon, 2003-12-15 at 09:37, D. Richard Hipp wrote: >(2) The ".dump" command will only show the binary data through >the first \000 character. If the binary data contains no >\000 characters, the ".dump" command might segfault. Add an SQL function like TOCHAR or something like