RE: [sqlite] DeviceSQL

2007-12-13 Thread Birt, Jeffrey
I concur. Quite an interesting marketing strategy; Join you competitors'
mailing lists and trash talk them. LOL

-Original Message-
From: dcharno [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 13, 2007 8:30 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] DeviceSQL

I would like to recommend that Encriq create a forum or mailing list of 
their own for those who are interesting in learning more.  For me, what 
might be an interesting product is quickly being overshadowed by this 
thread.


> 
> You raise some interesting points.  There is nothing secret about the
> benchmarks.  We will make the code that was used to run benchmarks
available
> to anyone who wants to see it and verify results. If you want to find
a
> third party to verify, be my guest. The benchmark report goes into
some
> depth on the design and rationale for the benchmark.  Frankly, as much
as I
> like the idea about taking DeviceSQL open source, you don't need to do
so,
> just to verify performance claims.  
> 
> Do you need to read the code to verify reliability as your next few
> sentences seems to imply? For that to be true, the reader would have
to be
> able to spot bugs through inspection.  While that is certainly one way
to
> spot bugs, I seriously doubt that any shop would rely on code
inspection,
> when millions of dollars of potential recall costs are on the line.
> 
> In fact the SQLite marketing does not rely on code inspection as its
> argument for why the code is reliable. Check it out. 
> 
> All of that said, I do admire the elegance of the SQLite code.  It
makes
> entertaining reading.  Unfortunately elegance does not translate into
> performance or reliability.
> 
> Regards,
> 
> Steve
> 
> James Steward-2 wrote:
>> steveweick wrote:
>>> Richard has it right this time.  Today DeviceSQL uses no SQLite
code. One
>>> of
>>> the things we might consider is bolting the SQLite parser/front end
to
>>> our
>>> table engine, in theory to get the both worlds.  Just an idea at the
>>> moment.
>>>   
>> Such an interesting discussion to be following.  I must say though,
it 
>> seems DeviceSQL has opened the door to speculation due to 
>> unsubstantiated claims in advertising, as far as I see it.  IMHO, so 
>> long as there is no independent, unbiased, side by side test results 
>> presented somewhere by some reliable source, there will always be
some 
>> room for "ifs" and "buts" by both sides.
>>
>> Maybe DeviceSQL should go open source, so the public can judge for
them 
>> selves the qualities of the two products.  There would still be money
to 
>> be made from paid support.  Who knows, both parties could benefit,
and 
>> customers too.  At least there'd be a clearer view of the pros and
cons. 
>>
>> There is something to be said for a product being open source, that
is 
>> the code is scrutinized by the world.  Closed shop code can possibly 
>> still be very good, but without seeing it, how would we know?
Reminds 
>> me of a story about a cat: dead or alive, we won't know until we open

>> the box it's in, and prior to that, is it only half dead?
>>
>> One only has to look at the MSDN code examples to see the ugliness of

>> closed source  code development...(sorry Bill)
>>
>> JS.
>>
>>

-
>> To unsubscribe, send email to [EMAIL PROTECTED]
>>

-
>>
>>
>>
> 



-
To unsubscribe, send email to [EMAIL PROTECTED]

-


-
To unsubscribe, send email to [EMAIL PROTECTED]
-



RE: [sqlite] Help for a newbie

2007-01-24 Thread Birt, Jeffrey



> -Original Message-
> From: Leonardo Mateo [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 24, 2007 4:02 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Help for a newbie
> 
> >
> > Thanks!  This is indeed a big help. I hope to be able to get back to
> > this project in the next few days.  The sources I got have the .def
> > file.  Are the 'development headers' a product of the build process?
> >
> I'm not sure I'm getting your question right. If you have the sources,
> you already have the development headers. In fact, those *.h files in
> the source tree are the "development headers" and all *.c files have
> the implementation of all functions defined in the header files.
> Once the library is compiled, you can "separate" files in the library
> and "development files" to package and distribute them but, when you
> have the source, as in your case, you have all you need there.
> 
> Maybe I'm misunderstanding your question, if so, please ignore what I
> said.
> 
> Cheers.
> 
> --
> Leonardo Mateo.
> There's no place like ~
> 

I was confused by the term development headers as used in the Qt ( used
it right that time :) ) docs, which read something like "You will need
the SQLite development headers and libraries installed before compiling
this plugin."  I thought perhaps this was referring to something other
than the source code header files.  

Thanks again,

Jeffrey T. Birt
Electronics Engineer
Integrated Systems Facility
University of Missouri - Rolla
573.341.6058



-
To unsubscribe, send email to [EMAIL PROTECTED]
-



RE: [sqlite] Help for a newbie

2007-01-24 Thread Birt, Jeffrey


>Hi, what you'll need to do is to build sqlite2 from sources with MinGW
>(Qt4 default compiler for Windows). Once you have this built, probably
>you will get an exe file and hopefully a shared library. (look at the
>sqlite install docs for instructions on how to build sqlite library)
>I've never done this job specifically, but I've done some similar
tasks.
>If you can't get sqlite shared library (.dll) built from sources you
>may get this library from SQLite site (I hope, I've done this with
>SQLite3).
>Once you have sqlite.dll you will have to generate .LIB file with
>MinGW tools, I can't remember specifically the sintax of gcc for this
>now, but take a look at gcc's command line help, but, basically you
>will need to generate a .def file from the .dll file and then with
>these files (.def and .dll) you will be able to generate .LIB file to
>link Qt4 plugin with it.
>
>Just a tip... please, say Qt, not QT. QT is owned by Mac
>
>Hope this help.
>
>Cheers.
>
>
>-- 
>Leonardo Mateo.
>There's no place like ~

Thanks!  This is indeed a big help. I hope to be able to get back to
this project in the next few days.  The sources I got have the .def
file.  Are the 'development headers' a product of the build process?


Jeffrey T. Birt
Electronics Engineer
Integrated Systems Facility
University of Missouri - Rolla
573.341.6058

-
To unsubscribe, send email to [EMAIL PROTECTED]
-



[sqlite] Help for a newbie

2007-01-22 Thread Birt, Jeffrey
Hello all,

I have been attempting to figure out how to build the sqlite2 plugin for QT4.  
I need to use V2 as I am working with files written by another program.  Here 
is a synopsis of where I am at:

I am a relitive newbie to QT et al (but not programming in general). I managed 
to downlaod/install/(build the debug files) for QT 4.2.2 open source. I found 
Qdevelop (IDE) installed it got the two to play nice a did a few 'Hello World' 
programs. (all on WinXP)

I then sat down and tried to write a simple program to access a SQLite V2 
database (becasue that is what another software package writes to and I need to 
work with those files). I read a bunch of the QT SQL library docs, wite a 
simple program and QT tells me that the driver (qsqlite2) for SQLite V2 is not 
available. So then I look up how to build the driver here: 
http://doc.trolltech.com/4.2/sql-driver.html, and basically says the following 
(instruction for V3 same as V2):

On Windows:
cd %QTDIR%\src\plugins\sqldrivers\sqlite

qmake -o Makefile "INCLUDEPATH+=C:\SQLITE\INCLUDE" 
"LIBS+=C:\SQLITE\LIB\SQLITE3.LIB" sqlite.pro

make

Looking at the readme in C:\Qt\4.2.2\src\plugins\sqldrivers\sqlite2 revealed 
this:

"You will need the SQLite development headers and libraries installed
before compiling this plugin."

So, I take it that I need the SQLite V2 sources. OK, I figured out how to get 
sqlite 2.8 downloaded from CVS. Now, that I have these sources how do I get 
them in the form that QT wants in order to build the plugin? In other words, 
the image of the files from CVS has no lib files or development headers (I 
think I have that right).  I have done a lot of searching but have not come up 
with anything. Can someone at least point me in the right direction. The 
sources I got from CVS do not have any type of library file(s) (which I'm 
guesing I need) Any help would be most appreciated.



Jeffrey T. Birt
Electronics Engineer
Integrated Systems Facility
University of Missouri - Rolla
573.341.6058 
http://web.umr.edu/~isf/
http://web.umr.edu/~autoid/
http://www.imscenter.net/


-
To unsubscribe, send email to [EMAIL PROTECTED]
-