Re: [sqlite] Improving performance of SQLite. Anyone heard of Devic eSQL?
Sqlite has Big names. May be this should be showcased at the sidebar on the front page. Does it need any other brand building activity? Atleast we got a better with those names. regards ragha ** This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! * - Original Message - From: John Elrick <[EMAIL PROTECTED]> Date: Monday, December 17, 2007 7:06 am Subject: Re: [sqlite] Improving performance of SQLite. Anyone heard of Devic eSQL? > John Stanton wrote: > > 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 bought except that you were the only ones > who > > convinced us you could do the job". We just smiled and watched > the > > ink dry while we pondered "where did we go right?". > > > > The simple truth is that if you hype a product and sell it into > an > > area where it is inadequate your triumph is short lived and the > scorn > > and litigation enduring. On the other hand if you deliver a > solution > > which works as well, or preferably better, than proposed you have > > generated raving fans who will buy again and endorse your product > to > > all and sundry. Which is the better model? > > To quote a former programs manager for Bank of America "the first > solution which meets my business needs and performs the job > adequately". In this case, adequately can be defined as loosely as > "doesn't crash too often" or as stringently as "positively no > errors", > depending on the business use. > > Keeping the discussion academic, "hype a product..." is a business > model > that apparently has been used to at least some degree by a company > called Microsoft. It tends to work because the model permits them > such > an early lead that even better products have difficulty catching up. > > I do most of my programming in Delphi, a Borland product which > remains > in my opinion, even in its shadow of former glory state, a far more > straightforward and powerful product than Visual Studio. Borland > has > always been a technical company, not a market driven one and its > flagship product is surviving only because it remains a more well > rounded Windows solution than its competition. However, it is only > surviving and is unlikely to actually thrive ever again. > > So my suggested answer is, the proven model is "dominate the market > early with an adequate product". If your product is very good and > even > better than proposed, all the better. But if you are "Johnny come > lately", you will likely lose unless your product is very, very > good. > And, whether we like it or not, a big part of market domination is > to > convince all the decision makers (management) and decision breakers > (engineers with influence) that yours is the safest choice to make. > > FWIW > > > John Elrick > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Improving performance of SQLite. Anyone heard of Devic eSQL?
John Stanton wrote: 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 bought except that you were the only ones who convinced us you could do the job". We just smiled and watched the ink dry while we pondered "where did we go right?". The simple truth is that if you hype a product and sell it into an area where it is inadequate your triumph is short lived and the scorn and litigation enduring. On the other hand if you deliver a solution which works as well, or preferably better, than proposed you have generated raving fans who will buy again and endorse your product to all and sundry. Which is the better model? To quote a former programs manager for Bank of America "the first solution which meets my business needs and performs the job adequately". In this case, adequately can be defined as loosely as "doesn't crash too often" or as stringently as "positively no errors", depending on the business use. Keeping the discussion academic, "hype a product..." is a business model that apparently has been used to at least some degree by a company called Microsoft. It tends to work because the model permits them such an early lead that even better products have difficulty catching up. I do most of my programming in Delphi, a Borland product which remains in my opinion, even in its shadow of former glory state, a far more straightforward and powerful product than Visual Studio. Borland has always been a technical company, not a market driven one and its flagship product is surviving only because it remains a more well rounded Windows solution than its competition. However, it is only surviving and is unlikely to actually thrive ever again. So my suggested answer is, the proven model is "dominate the market early with an adequate product". If your product is very good and even better than proposed, all the better. But if you are "Johnny come lately", you will likely lose unless your product is very, very good. And, whether we like it or not, a big part of market domination is to convince all the decision makers (management) and decision breakers (engineers with influence) that yours is the safest choice to make. FWIW John Elrick - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Compiling Problem With SQLite 3.5.4
Zbigniew Baniewski wrote: On Sat, Dec 15, 2007 at 12:48:44PM -0500, Robert L Cochran wrote: I did a poor job of explaining this issue. GCC builds of 3.5.4 seem to fail. I've sent Richard a bunch of log files comparing source code builds of versions 3.5.3 and 3.5.4 showing what I believe are symptoms of the alleged failure. If anyone wants copies of the same set of files, feel free to contact me. Just out of curiosity made a compilation of 3.5.4: apart of some warnings (below) no errors at all. cp: uwaga: plik źródłowy `./src/btree.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./src/hash.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./src/sqliteInt.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./src/vdbe.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./ext/fts1/fts1.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./ext/fts1/fts1_hash.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./ext/fts1/fts1_tokenizer.h' pojawił się więcej niż raz (it means: "cp: warning: source file `..' appears more than once") Compiled on: gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) Linux with kernel 2.6.22 Pentium II One additional comment: Tcl's 8.5 "package require" isn't as tollerant about version marks, as in 8.4.x line it used to. So, the proper pgIndex.tcl contents should contain the subversion digit as well, instead of just "3.5" - I mean: package ifneeded sqlite3 3.5.4 [list load /usr/local/lib/tcl8.5/sqlite3/libtclsqlite3.so sqlite3] Yes, I agree completely. 'make' wasn't issuing the 'creating sqlite3' message I've been so accustomed to, and the cp messages about duplicates concerned me. Christian supplied me some patches to get rid of the size messages and Richard told me they got rid of the creating message, 'make install' worked fine, and I have version 3.5.4 (with Christian's patches) running. Bob - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Compiling Problem With SQLite 3.5.4
On Sat, Dec 15, 2007 at 12:48:44PM -0500, Robert L Cochran wrote: > I did a poor job of explaining this issue. GCC builds of 3.5.4 seem to > fail. I've sent Richard a bunch of log files comparing source code > builds of versions 3.5.3 and 3.5.4 showing what I believe are symptoms > of the alleged failure. If anyone wants copies of the same set of files, > feel free to contact me. Just out of curiosity made a compilation of 3.5.4: apart of some warnings (below) no errors at all. cp: uwaga: plik źródłowy `./src/btree.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./src/hash.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./src/sqliteInt.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./src/vdbe.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./ext/fts1/fts1.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./ext/fts1/fts1_hash.h' pojawił się więcej niż raz cp: uwaga: plik źródłowy `./ext/fts1/fts1_tokenizer.h' pojawił się więcej niż raz (it means: "cp: warning: source file `..' appears more than once") Compiled on: gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) Linux with kernel 2.6.22 Pentium II One additional comment: Tcl's 8.5 "package require" isn't as tollerant about version marks, as in 8.4.x line it used to. So, the proper pgIndex.tcl contents should contain the subversion digit as well, instead of just "3.5" - I mean: package ifneeded sqlite3 3.5.4 [list load /usr/local/lib/tcl8.5/sqlite3/libtclsqlite3.so sqlite3] -- pozdrawiam / regards Zbigniew Baniewski - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] Improving performance of SQLite. Anyone heard of DeviceSQL?
> 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 > bought except that you were the only ones who convinced us > you could do the job". We just smiled and watched the ink > dry while we pondered "where did we go right?". > > The simple truth is that if you hype a product and sell it > into an area where it is inadequate your triumph is short > lived and the scorn and litigation enduring. On the other > hand if you deliver a solution which works as well, or > preferably better, than proposed you have generated raving > fans who will buy again and endorse your product to all and > sundry. Which is the better model? I agree that if its an inadaquate product, the deep stuff you get into is well deserved (but you clearly connected with someone who did understand the technical value so it isnt entirely hopeless a situation). I do not see a choice here - you need great technology and you need just the right marketing to maximize your own return and push out the limits of what your company can achieve. Convince both management and engineering. They both need to be on the same page or else, and I think that is achievable. Engineers making all decisions may sound like its sensible but its asking for a different type of trouble. Years ago I was involved with a large corporation that dominated a particular market space (about 10 million seats circa 1996). An engineer solved a problem by using a third party control that he didn't run by corporate before incorporating into the product. That engineer did not understand that all portions of the product had to meet specific criteria in European and Asian markets - that control was totally incompatible, and the source wasn't available at any price (this was fairly well spelled out in the EULA after the problem surfaced). The discovery wasn't made until after North American launch, and late in process when European and Asian launches were developed. The re-engineering costs and unexpected delays in those markets had a severe financial impact. Yes, this is just one instance - but just one of many. I think the availability of inexpensive overseas development is a wake up call to engineers in North America and Western Europe that they have to move to engage management (ie be a part of management). On the other hand, management that jumps into outsourcing without a good understanding of architectural goals and architectural management learn to regret it. Best regards, Lynn Fredricks President Paradigma Software http://www.paradigmasoft.com Valentina SQL Server: The Ultra-fast, Royalty Free Database Server - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Amalgamation and g++
This is not a link issue, but a compiler one. SQLite is ANSI C, so you
should compile it with gcc. It will still be usable within your C++
library/project, as sqlite3.h qualifies all functions extern "C".
For example, given a C++ file main.cpp:
#include
int main()
{
sqlite3* db;
sqlite3_open("foo.db", );
sqlite3_close(db);
return 0;
}
Build it as follows:
gcc -c sqlite3.c
g++ -c main.cpp
g++ -o program main.o sqlite3.o -lpthread -ldl
Just make sure you associate .c files with gcc in your makefile and
this will be taken care of for you automatically. Something like:
.cpp.o:
$(CPP) -c $(CPPFLAGS) $<
.c.o:
$(CC) -c $(CFLAGS) $<
-- Mike
On Dec 16, 2007 11:50 AM, David Gelt <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I have compiled version 3.5.2 of the amalgamation in C without any errors or
> warnings but when I am trying to do the same in C++ using g++ I keep getting
> lots of errors and warnings. I have -ldl -lpthread in Makefile and running
> Fedora Core 6.
>
> Here are some reported errors and warnings:
> ./sqlite3.c:4265: error: uninitialized const 'sqlite3One'
> ../sqlite3.c: In function 'void computeJD(DateTime*)':
> ../sqlite3.c:7241: warning: converting to 'int' from 'double'
> .
> ../sqlite3.c: In function 'void strftimeFunc(sqlite3_context*, int,
> sqlite3_value**)':
> ../sqlite3.c:7840: error: invalid conversion from 'void*' to 'char*'
> .
>
> Do I need to define other flags or do something else?
>
> Thanks in advance.
>
> Regards,
> David
>
>
> -
> Looking for last minute shopping deals? Find them fast with Yahoo! Search.
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
RE: [sqlite] Improving performance of SQLite. Anyone heard of DeviceSQL?
> My intent is to provide complete detailed technical > information about SQLite, including its limitations and > faults, and honest comparisons and even recommendations of > other products (including, but not limited to DeviceSQL). My > intent is to avoid sophistry, misrepresentation, > exaggeration, and hype. > This intent is sometimes imperfectly executed, but it is my goal. > > If that means that SQLite is uncompetitive, then so be it. I wasn't criticizing what you did, only stating that sales people often target decision makers who are not engineers and its an inevitability in commercial software sales. I think SQLite falls out of the norm anyway - there are plenty of commercial products that incorporate the public domain source code and leverage public knowledge of SQLite that are totally outside of your control or influence. With many products, who knows what's been changed anyway? You cant be responsible for that :-) Best regards, Lynn Fredricks President Paradigma Software http://www.paradigmasoft.com Valentina SQL Server: The Ultra-fast, Royalty Free Database Server - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Default Encoding In Sqlite
Sorry.. meant English is NOT my primary language :) Daniel Önnerby wrote: 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 is created (sqlite3_open or sqlite3_open16). SQLite will also seamlessly convert between the different formats depending on how you retrieve the texts (sqlite3_column_text or sqlite_column_text16) regardless on what format it has been saved as. There are some cases -like using case insensitive LIKE- where SQLite needs to be extended with the ICU extension to fully work with unicode strings. [EMAIL PROTECTED] wrote: =?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 <[EMAIL PROTECTED]> - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] - - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] BOOLEAN DEFAULT VALUE
The documentation is obscure on that point. Than you. Brad Stiles wrote: > >> I got a BOOLEAN field. It's defined: NOT NULL. >> >> when a new record is inserted, how to put a Boolean Default Value >> as FALSE? > > By reading the documentation. > > http://www.sqlite.org/lang_createtable.html > http://www.sqlite.org/lang_createtrigger.html > > > Brad > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/BOOLEAN-DEFAULT-VALUE-tp14361417p14362729.html Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] BOOLEAN DEFAULT VALUE
Thank you. Igor Tandetnik wrote: > > Runspect <[EMAIL PROTECTED]> wrote: >> I got a BOOLEAN field. It's defined: NOT NULL. >> >> when a new record is inserted, how to put a Boolean Default Value as >> FALSE? > > SQLite doesn't have a dedicated boolean type. You just store them as > integer, zero for false and nonzero for true. So make it > > create table myTable(col BOOLEAN default 0); > > Igor Tandetnik > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > - > > > -- View this message in context: http://www.nabble.com/BOOLEAN-DEFAULT-VALUE-tp14361417p14362620.html Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] Re: BOOLEAN DEFAULT VALUE
Runspect <[EMAIL PROTECTED]> wrote: I got a BOOLEAN field. It's defined: NOT NULL. when a new record is inserted, how to put a Boolean Default Value as FALSE? SQLite doesn't have a dedicated boolean type. You just store them as integer, zero for false and nonzero for true. So make it create table myTable(col BOOLEAN default 0); Igor Tandetnik - To unsubscribe, send email to [EMAIL PROTECTED] -
RE: [sqlite] BOOLEAN DEFAULT VALUE
> I got a BOOLEAN field. It's defined: NOT NULL. > > when a new record is inserted, how to put a Boolean Default Value > as FALSE? By reading the documentation. http://www.sqlite.org/lang_createtable.html http://www.sqlite.org/lang_createtrigger.html Brad - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] BOOLEAN DEFAULT VALUE
I got a BOOLEAN field. It's defined: NOT NULL. when a new record is inserted, how to put a Boolean Default Value as FALSE? Thanks. -- View this message in context: http://www.nabble.com/BOOLEAN-DEFAULT-VALUE-tp14361417p14361417.html Sent from the SQLite mailing list archive at Nabble.com. - To unsubscribe, send email to [EMAIL PROTECTED] -
