On 10/28/05, Joe Wilson <[EMAIL PROTECTED]> wrote:
> --- Nuno Lucas <[EMAIL PROTECTED]> wrote:
> > On 10/25/05, Joe Wilson <[EMAIL PROTECTED]> wrote:
> > > The built-in Sqlite length() function works just fine on blobs:
> > >
> > > sqlite> select length(X'00');
> > > 5
> > >
> > > Why
On 10/31/05, Fred Williams <[EMAIL PROTECTED]> wrote:
> Look I'm certain you mean well, but the rest of us are pretty busy using
> one of the best small footprint databases on the planet. That means we
> are way too busy to nit-pic a good product to pieces, just because it
> won't compile clean
I have been silently reading the conversation, but I have
to reply on this latest message.
- Original Message -
From: "Fred Williams" <[EMAIL PROTECTED]>
Look I'm certain you mean well, but the rest of us are pretty busy using
one of the best small footprint databases on the planet.
Fred,
They are not nit-picking and they "are" actually contributing to the
robustness of the application by doing this research. Your
anti-Microsoft bigotry does no service to this list at all and is
neither a "contribution" or an offer of help.
I for one would be keen to see these warnings
hello.
i have sqlite 2.8.17 installed on my system (compiled manually not a distro
package)
i wish to remove it (uninstall) it complitlly from my system and install the
3.2.7
i need to make sure it is removed so i can make sure that the program i need
to install that will use sqlite will be
On Mon, 31 Oct 2005, Adi Spivak wrote:
>
>hello.
>i have sqlite 2.8.17 installed on my system (compiled manually not a distro
>package)
>i wish to remove it (uninstall) it complitlly from my system and install the
>3.2.7
>i need to make sure it is removed so i can make sure that the program i
What is important is the implication of the compile warnings. I agree
that they should not be ignored, but they should be understood. For
example we always take pains to remove all compiler warnings, even the
innocuous and gratuitous ones, so that "noise" does not hide a
significant warning.
That's exactly what I ended up doing in the ADO.NET 2.0 wrapper. In order
to implement full Compact Framework support and callbacks, I ended up
writing stdcall entrypoints and callback wrappers for just about the entire
SQLite API.
Robert
- Original Message -
From: "Arjen Markus"
> Look I'm certain you mean well, but the rest of us are pretty busy
using
> one of the best small footprint databases on the planet. That means
we
> are way too busy to nit-pic a good product to pieces, just because it
> won't compile clean using Mickeysoft's latest and greatest.
It's not a
Length() is perfectly consistant with the value's type. As you've
demonstrated, Sqlite does not respect the column types in tables
as declared in the CREATE statement.
Length(text_value) always returns the number of characters and
length(blob_value) always returns the number of bytes. The type
I had this same problem some time ago. We were trying to make a virtual list
box that could handle ANY number of items. The scroll bar is the wrinkle. You
can't set it or size it without knowing the size of the list.
My conclusion was this:
A list of more than 100 or so items on screen is really
I'm certainly not diplomatic material. But, what you have said is
exactly what I meant. I get more than a little weary of people who take
"free" code and whine about it. My belief is if you don't like it, fix
it yourself or shut up after your initial "notification" of the issue.
As to calling
Robert Simpson wrote:
>
> That's exactly what I ended up doing in the ADO.NET 2.0 wrapper. In order
> to implement full Compact Framework support and callbacks, I ended up
> writing stdcall entrypoints and callback wrappers for just about the entire
> SQLite API.
>
My Fortran interface does
Oops - the second paragraph should have read:
"with appropriate manipulations of sqlite3_value_type(),
sqlite3_value_bytes() and sqlite3_value_text()."
--- Joe Wilson <[EMAIL PROTECTED]> wrote:
> Length() is perfectly consistant with the value's type. As you've
> demonstrated, Sqlite does not
Hello,
I would like to know how I should handle dates and timestamps
via the C API. I know that if I write an SQL insert statement, I have
to use one of the forms reserved for dates and timestamps and
the like, but how do I do this via the sqlite3_bind_* procedures?
Regards,
Arjen
On 30 Oct 2005 at 03:14 NZST, Florian Weimer wrote:
> Is it true that there isn't yet a binding to SQLite versoin 3 from
> Objective Caml?
>
> (I only found one for version 2.)
There seem to be a couple of different ocaml-sqlite3 bindings around:
Is it really necessary for copy's input file to be fopen()ed with mode
"rb"? This causes CRLF files opened on MS-Windows to have \r's appended
to the values in the last column. The last column might otherwise be
numeric.
Actually, I'd prefer that DB_COPY accept a Tcl channel rather than a
We use a TEXT field for dates and time and make it strictly ISO8601 and
hence portable between storage methods.
Jay Sprenkle wrote:
I would like to know how I should handle dates and timestamps
via the C API. I know that if I write an SQL insert statement, I have
to use one of the forms
>I simply count the number of elements in my record set
>thereby avoiding a double query to the database.
Yes, exactly, I take for granted that the resultset is accumulated at the
database level and not
at the application level.
-
ed
--- Puneet Kishor <[EMAIL PROTECTED]> wrote:
>
> On Oct
On Oct 31, 2005, at 7:54 PM, Edward Wilson wrote:
I simply count the number of elements in my record set
thereby avoiding a double query to the database.
Yes, exactly, I take for granted that the resultset is accumulated at
the database level and not
at the application level.
sorry, I
20 matches
Mail list logo
