I have opened a ticket (#1147) for the full_column_names issue, which is back
in 3.1.3. pls check it out.
also, I noticed the following :
when selecting from a view, and duplicate column names exist, there is an
attempt to de-dupe them, by adding a sequence number, like this:
ID ID:1 ID:2
Hi,
I've been trying to modify the ODBC driver
(http://www.ch-werner.de/sqliteodbc/) to be able to work with BLOBs. The current
0.65 ODBC driver can only handle CLOBs (i.e. null terminated strings) inspite
of it being built on sqlite3 .
I've managed to get BLOB writing to work by using
On Mon, 2005-02-28 at 11:12 +0200, Cariotoglou Mike wrote:
> I understand that this "column names" issue is becoming a pain for the
> sqlite authors, but OTOH, it is very important for wrapper authors...
>
Why? Why does anybody care what the column names in the result
are? What are the column
D. Richard Hipp said:
> On Mon, 2005-02-28 at 11:12 +0200, Cariotoglou Mike wrote:
>> I understand that this "column names" issue is becoming a pain for the
>> sqlite authors, but OTOH, it is very important for wrapper authors...
>>
>
> Why? Why does anybody care what the column names in the
Speaking as a wrapper writer myself (VB Wrapper), I too don't need or make
any use of the column names but I can see where they might be being used by
other wrappers e.g. ODBC/ADO/OLEDB.
It's a convenient way for these guys to pick up field name bindings from
select statements i.e. it saves them
On Sat, 28 Feb 2004 11:52:03 +0100, Jakub Adamek <[EMAIL PROTECTED]> wrote:
> Is it really so that some database server returns a result set with two
> same column names? Seems very strange. And the lovely SQLite 3.0.8
> didn't do such things ...
PostgreSQL, which holds closer to the SQL spec
> -Original Message-
> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 5:38 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] ticket 1147
>
> On Mon, 2005-02-28 at 11:12 +0200, Cariotoglou Mike wrote:
> > I understand that this "column names"
Has anyone used SQLite to store XML fragments or documents? Which approach
have you taken or what approach would you take? I am currently evaluating
the possibilities of storing arbitrary XML fragments using SQLite. The
fragments may or may not have schema information.
Hello SQLiters!
I am trying to figure out "best practices" for accessing SQL Tables from
other servers in the same LAN with bandwidth of 1 GB.
There are several purposes for such access:
1) to query tables from one of the servers running HTTP-Daemon (apache)
using perl.
2) to read entire table
I use column names. I have created a wrapper around sqlite3 (and other
SQL engines) in a developmeny environment I have written to enable the
programmer (or user for that matter) to access an SQL result set using
an object where the property names are the column names.
However - having
> -Original Message-
> From: Edward Macnaghten [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 16:47
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] ticket 1147
> However - having duplicate column names (without aliasing
> them), or using an unqualified "*" when querying a
Edward Macnaghten wrote:
I use column names. I have created a wrapper around sqlite3 (and
other SQL engines) in a developmeny environment I have written to
enable the programmer (or user for that matter) to access an SQL
result set using an object where the property names are the column names.
On Mon, Feb 28, 2005 at 05:05:37PM -, Tim Anderson wrote:
> SELECT Name, Title, Books.ID, Authors.ID FROM Books inner join Authors
> on Books.AuthorID = Authors.ID ORDER BY Authors.Name, Books.Title;
>
> In this case, the query is unambiguous, but by default Sqlite returns
> the column names
On Mon, 2005-02-28 at 08:48 -0700, Robert Simpson wrote:
> 5. What we do with the schema information or how well we compute it is
> irrelevant.
>
No. It is exceedingly relevant if you want any cooperation from
me in addressing the issue.
There seem to be a lot of people who are emphatic
> -Original Message-
> From: Andrew Piskorski [mailto:[EMAIL PROTECTED]
> Sent: 28 February 2005 17:28
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] ticket 1147
>
> On Mon, Feb 28, 2005 at 05:05:37PM -, Tim Anderson wrote:
>
> > SELECT Name, Title, Books.ID, Authors.ID FROM
D. Richard Hipp wrote:
Can nobody give me a use case where it is important
to know what the originating column for a result set value is?
Any wrapped or API that loads row values into a hash, and if some
columns have
exactly the same names then they would overwrite information in the
hash.
> -Original Message-
> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 11:30 AM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
>
> On Mon, 2005-02-28 at 08:48 -0700, Robert Simpson wrote:
> > 5. What we do with the schema information
On Mon, Feb 28, 2005 at 05:38:24PM -, Tim Anderson wrote:
> > > SELECT Name, Title, Books.ID, Authors.ID FROM Books inner
> > join Authors
> > > on Books.AuthorID = Authors.ID ORDER BY Authors.Name, Books.Title;
> Not quite. You wanted the column called "Books.ID" so that was
> specified.
> > On Mon, 2005-02-28 at 08:48 -0700, Robert Simpson wrote:
> > > 5. What we do with the schema information or how well we
> > compute it
> > > is irrelevant.
> > >
> >
> > No. It is exceedingly relevant if you want any cooperation
> > from me in addressing the issue.
> >
> > There seem
> -Original Message-
> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 10:30 AM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
>
> On Mon, 2005-02-28 at 08:48 -0700, Robert Simpson wrote:
> > 5. What we do with the schema information
On Mon, Feb 28, 2005 at 09:58:15AM -0800, Tim McDaniel wrote:
> Given a specific SELECT statement, ADO.NET has the capability to
> automatically build the corresponding INSERT, UPDATE, and DELETE
> statements, so the user can insert/update/delete values/rows in the
> resultset and have those
On Mon, Feb 28, 2005 at 11:16:33AM -0700, Robert Simpson wrote:
> Here are just a few things I can think of off the top of my head that I
> cannot do right now for a resultset, but that I *can* do with additional
> schema information:
Do you mean that you would like additional schema information
Jay said:
> Interesting!
> How do they handle calculated columns and constraints and such?
> Does it just fail?
Most ADO wrappers cough up a hairball and refuse to proceed. That is,
coincidentally, what should be done when you're trying to update a dataset
that resulted from a join. Unless
> -Original Message-
> From: Jay [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 11:08 AM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
>
> > > On Mon, 2005-02-28 at 08:48 -0700, Robert Simpson wrote:
> > > > 5. What we do with the schema information or
Well, I can help here a little, having provided meta data for 11 different
databases via our product MyGeneration. We do support SQLite too,
including foreignkeys and all the good stuff. However, concerning columns
contained results sets from say a select statement that's another story,
you're
> -Original Message-
> From: Andrew Piskorski [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 11:17 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] ticket 1147
>
> On Mon, Feb 28, 2005 at 09:58:15AM -0800, Tim McDaniel wrote:
>
> > Given a specific SELECT statement,
Is there a good enterprise manager like tool for SQLite 3.0? I'm a
windows guy and command line impaired, what I'm really after is a database
with a column in it that use the new AUTOINCREMENT keyword, we're adding
support for SQLite 3.x in MyGeneration, we'll also be releasing an
instance of our
I didn't find anything in the archives, but is there a reason that the
sql_exec_printf wasn't carried over from sqlite2 to sqlite3?
I figure I can add the functions back in, but is there a better way
intended to implement the same functionality, without adding the functions?
Thanks for the
> -Original Message-
> From: Andrew Piskorski [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 11:34 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] ticket 1147
>
> On Mon, Feb 28, 2005 at 11:16:33AM -0700, Robert Simpson wrote:
>
> > Here are just a few things I can
Hello,
vdbemem.c (2004 May 26) reads at about line 650:
if( pMem->enc==SQLITE_UTF8 && (flags & MEM_Term) ){
assert( strlen(pMem->z)<=pMem->n );
assert( pMem->z[pMem->n]==0 );
}
First is tested if the length of the passed string is shorter or equal to
the passed
> -Original Message-
> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 10:30 AM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
[snip]
> What do
> other database engines (PostgreSQL, Oracle, MySQL) do in the way
> of revealing the
> Metadata should be on-demand, and not automatically returned. As far as a
> standard is concerned, OLEDB and ODBC do it differently and I'd have to
> look it up.
Here are the meta data standards:
OLEDB Scheme Rowsets
On Mon, 2005-02-28 at 11:54 -0700, Robert Simpson wrote:
> Column Name - The name of the column as specified in the SELECT clause and
> what SQLite already generates
> Base Table - The base table the column came from or NULL if the column was
> computed
> Base Column - The base column of the table
> -Original Message-
> From: Robert Simpson [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 12:55 PM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
>
> > -Original Message-
> > From: Andrew Piskorski [mailto:[EMAIL PROTECTED]
> > Sent: Monday,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 12:26 PM
> To: sqlite-users@sqlite.org
> Cc: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
>
> > Metadata should be on-demand, and not automatically
> returned.
> -Original Message-
> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 12:25 PM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] ticket 1147
>
> On Mon, 2005-02-28 at 11:54 -0700, Robert Simpson wrote:
> > Column Name - The name of the column as
At 8:32 AM -0500 2/28/05, Clay Dowling wrote:
D. Richard Hipp said:
On Mon, 2005-02-28 at 11:12 +0200, Cariotoglou Mike wrote:
I understand that this "column names" issue is becoming a pain for the
sqlite authors, but OTOH, it is very important for wrapper authors...
Why? Why does anybody
Robert Simpson wrote:
>> -Original Message-
>> From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
>> Sent: Monday, February 28, 2005 10:30 AM
>> To: sqlite-users@sqlite.org
>> Subject: RE: [sqlite] ticket 1147
>
> [snip]
>> What do
>> other database engines (PostgreSQL, Oracle, MySQL) do in
At 12:29 PM -0500 2/28/05, D. Richard Hipp wrote:
What about the result set
of compound selects or of natural joins where the origin column
is ambiguous? If knowing the original column is so important,
what do people do with those cases?
Since this was brought up, I'll answer it as a separate
> I'll third Dr. Hipp's statement.
>
> I have my own wrappers (in Perl), made for public
> consumption, and never had problems with returned column names.
>
> Simply put, the elegant solution for wrapper authors is to
> always use 'as' to explicitly define the column names you
> want. You
On Mon, 2005-02-28 at 20:03 +0100, Bernhard DÃbler wrote:
> Hello,
>
> vdbemem.c (2004 May 26) reads at about line 650:
>
> if( pMem->enc==SQLITE_UTF8 && (flags & MEM_Term) ){
> assert( strlen(pMem->z)<=pMem->n );
> assert( pMem->z[pMem->n]==0 );
> }
>
> First is
SQLiters:
does anybody have a need to access SQLite Tables on a different server over
the same LAN?
how do you access such Tables?
Regards,
Uriel_Carrasquilla
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 12:43 PM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] Good Graphical Tool for 3.x
>
> Is there a good enterprise manager like tool for SQLite 3.0?
> I'm a windows guy and
For me it is not important to know from which table the column comes,
but it is a must to have unique column names - because I address all
columns by their names. I could also use the column order but this would
lead to worse readability and maintainability. Therefore my wrapper
protests when
The SqlitePlus Database Manager is pretty good. Its very similar to Microsoft
SQL Query Analyzer. Here is the URL:
www.sqliteplus.com
Quoting Tim McDaniel <[EMAIL PROTECTED]>:
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]
> > Sent: Monday,
On Mon, 2005-02-28 at 19:14 -0400, [EMAIL PROTECTED] wrote:
> >
> How about the sqlite3_mprintf and sqlite3_vmprintf functions? are they
> for the legacy users only?
>
It is unclear how to add UTF-16 support to those functions.
But they are used internally so they are unlikely to go away.
--
I type very fast and my fingers added the semicolon on the end
because they're used to doing it:
sqlite> .dump people_event;
BEGIN TRANSACTION;
COMMIT;
sqlite> .dump people_event
BEGIN TRANSACTION;
CREATE TABLE People_Event
(
PeopleINTEGER NOT NULL,
Event
D. Richard Hipp wrote:
On Mon, 2005-02-28 at 19:14 -0400, [EMAIL PROTECTED] wrote:
How about the sqlite3_mprintf and sqlite3_vmprintf functions? are they
for the legacy users only?
It is unclear how to add UTF-16 support to those functions.
But they are used internally so they are
D. Richard Hipp wrote:
On Mon, 2005-02-28 at 11:54 -0700, Robert Simpson wrote:
Column Name - The name of the column as specified in the SELECT clause and
what SQLite already generates
Base Table - The base table the column came from or NULL if the column was
computed
Base Column - The base
[EMAIL PROTECTED] wrote:
D. Richard Hipp wrote:
On Mon, 2005-02-28 at 19:14 -0400, [EMAIL PROTECTED] wrote:
How about the sqlite3_mprintf and sqlite3_vmprintf functions? are
they for the legacy users only?
It is unclear how to add UTF-16 support to those functions.
But they are used
> > Regarding the sqlite3_exec() should no longer be used for sqlite3 for
> > Unicode application. I am doing the "Begin Transaction" "Commit
> > Transaction"... with the sqlite3_exec(), since this function not
> > supporting Unicode, do you show me how to do a transaction with
> > sqlit3.
Thanx, I tried that would last night, unfortunately the trial version is
so crippled its worthless.
>
> The SqlitePlus Database Manager is pretty good. Its very similar to
> Microsoft
> SQL Query Analyzer. Here is the URL:
>
> www.sqliteplus.com
>
>
> Quoting Tim McDaniel <[EMAIL
I used this SQL:
CREATE TABLE NewEmployees(EmployeeID INTEGER PRIMARY KEY AUTOINCREMENT,
LastName TEXT, FirstName TEXT);
and using SQLite3.exe did this
SQLite3 employees.db
.read create.sql
.exit
which created my database but no tools nor the SQLite.NET provider can
read it, I get the error
Here are some alternate API naming suggestions, that I have thought
through at length and believe will work.
Since the proposed new functions are all related and talk about the
source table or view columns for the query, they should all have the
word 'source' in their names. Here are my
I downloaded sqlite-3.1.3 and made the fix. The patch is attached.
Also created a ticket here:
http://www.sqlite.org/cvstrac/tktview?tn=1151
-Charlie
On Feb 16, 2005, at 2:15 PM, Charles Mills wrote:
open the database "test.db"
then execute the following sql commands
ATTACH 'test.db' AS hey
> -Original Message-
> From: Darren Duncan [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 10:29 PM
> To: sqlite-users@sqlite.org
> Subject: [sqlite] new API for query column sources (was Re:
> ticket 1147)
>
> Here are some alternate API naming suggestions, that I have
>
This patch doesn't have the memory leak the other one has and it is
formatted correctly.
Sorry about that :)
-Charlie
On Feb 28, 2005, at 10:05 PM, Charles Mills wrote:
This patch doesn't have the memory leak the other one has and it is
formatted correctly.
Sorry about that :)
whoops.
-Charlie
Sure, an API for returning result set info would be fine, and more convenient
than these pragmas, which for one thing are stateful, and thus hell for wrapper
writers, which need to assume that only the *wrapper* may set these pragmas.
Also, in order to avoid API explosion, I feel that a single
>
> Simply put, the elegant solution for wrapper authors is to always use
> 'as' to explicitly define the column names you want. You always know
> how these names map to original table columns because you explicitly
> said so.
It isn't as simply as that. I.e. within the Delphi wrapper users can
60 matches
Mail list logo
