A good salesman taught me - "When you have made the sale, stop selling".
If you have identified "The Fox" (the hidden actual decision maker)
and made your case with an erudite technical presentation all the rest
is just noise, and can even be detrimental. After all 'decent
marketing" is measu
* John Stanton <[EMAIL PROTECTED]> [2007-12-15 22:55]:
> Which is the better model?
False dilemma. Where there is a budget, there is no reason you
can’t have both a good product and at least decent marketing.
Even when the product isn’t good, it’s unlikely to be so useless
as to violate the terms
I figure I'll keep it short since it's only for the FAQ.
English is my primary language, but here my suggestion:
Question: Does SQLite handle unicode?
Short answer: Yes!
Answer:
SQLite handles unicode very well. SQLite stores texts in either UTF-16
or UTF-8 format depending on how the database
[EMAIL PROTECTED] wrote:
Joe Wilson <[EMAIL PROTECTED]> wrote:
--- [EMAIL PROTECTED] wrote:
Joe Wilson <[EMAIL PROTECTED]> wrote:
The reason why I asked is that I haven't had much luck with sqlite3
performance for databases larger than the size of RAM on my machine
regardless of PRAGMA settin
This also is an anecdote from some time back. As we were signing a
fairly significant software contract with a large organization their
manager told us "You guys know nothing about marketing. Your
presentation was unprofessional, no glossy brochures, no audio visuals
and we would not have bou
--- [EMAIL PROTECTED] wrote:
> The problem is when inserting into large database that is
> indexed, the values being indexed are randomly distributed.
> So with each insert, SQLite has to seek to a new random
> place in the file to insert the new index entry there.
> It does not matter that pages o
=?ISO-8859-1?Q?Daniel_=D6nnerby?= <[EMAIL PROTECTED]> wrote:
> Unicode questions seems to come up at least once a week on the
> mailinglist. Maybe there should be something about this in the FAQ or
> the features page?
>
I will happily accept suggested text for such entries.
--
D. Richard Hipp
Following patch applied to the CVS version compiled
w/o warnings on a CentOS 5 x86_64 box. But I didn't
run the test yet ... and autoconf logic regarding
availability of ptrdiff_t is missing, too.
Index: src/func.c
===
RCS file: /sqli
Joe Wilson <[EMAIL PROTECTED]> wrote:
> --- [EMAIL PROTECTED] wrote:
> > Joe Wilson <[EMAIL PROTECTED]> wrote:
> > > The reason why I asked is that I haven't had much luck with sqlite3
> > > performance for databases larger than the size of RAM on my machine
> > > regardless of PRAGMA settings.
>
[EMAIL PROTECTED] wrote:
Robert L Cochran <[EMAIL PROTECTED]> wrote:
While compiling version 3.5.4 using gcc, I got these messages from
'make' on my CentOS 5 host. It looks to me like the 'make' step failed.
I can post the config.log if that would help.
How can I fix this to get a successf
[EMAIL PROTECTED] wrote:
>
> Christian Werner <[EMAIL PROTECTED]> wrote:
> >
> > What about using the ptrdiff_t type in those places instead.
> >
>
> Is ptrdiff_t implemented on all C compiler environments that
> SQLite builds on?
I'm afraid not, thus some autoconf logic might be required to
det
On Dec 14, 2007, at 9:24 PM, Lynn Fredricks wrote:
That's true. A lot of those kinds of sales presentations are correctly
targeted at decision makers that make financial decisions. I don't
consider
it a bad thing - it's really a necessity to be competitive. The bear
in the
woods isnt evil,
Unicode questions seems to come up at least once a week on the
mailinglist. Maybe there should be something about this in the FAQ or
the features page?
Trevor Talbot wrote:
I wrote:
The default storage encoding on disk is UTF-8, but it can be changed
to UTF-16 with a PRAGMA.
As Igo
--- [EMAIL PROTECTED] wrote:
> Joe Wilson <[EMAIL PROTECTED]> wrote:
> > The reason why I asked is that I haven't had much luck with sqlite3
> > performance for databases larger than the size of RAM on my machine
> > regardless of PRAGMA settings.
>
> This is probably do to the cache locality pro
Christian Werner <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
> > ...
> > The warnings all have to do with the fact that you are
> > compiling on a machine with 64-bit pointers and 32-bit
> > integers. The warnings are all harmless and the code
> > works as intended as long as
> >
> >
[EMAIL PROTECTED] wrote:
> ...
> The warnings all have to do with the fact that you are
> compiling on a machine with 64-bit pointers and 32-bit
> integers. The warnings are all harmless and the code
> works as intended as long as
>
> sizeof(int) <= sizeof(void*)
>
> Perhaps a reader can s
Robert L Cochran <[EMAIL PROTECTED]> wrote:
> While compiling version 3.5.4 using gcc, I got these messages from
> 'make' on my CentOS 5 host. It looks to me like the 'make' step failed.
> I can post the config.log if that would help.
>
> How can I fix this to get a successful compile?
>
I don
While compiling version 3.5.4 using gcc, I got these messages from
'make' on my CentOS 5 host. It looks to me like the 'make' step failed.
I can post the config.log if that would help.
How can I fix this to get a successful compile?
Bob Cochran
./libtool --mode=link gcc -g -O2 -I. -I../sr
This discussion reminds me of another long, long ago in a galaxy far,
far away. (When I worked on "Mainframes" with 32 K or less "core"
memory.)
Discussing the then lopsided world with my non-IBM salesman, in a local
watering hole, after a particularly trying day of dealing with
"management." The
On Dec 14, 2007, at 9:24 PM, Lynn Fredricks wrote:
That's true. A lot of those kinds of sales presentations are correctly
targeted at decision makers that make financial decisions. I don't
consider
it a bad thing - it's really a necessity to be competitive.
My intent is to provide comple
20 matches
Mail list logo
