Re: [sqlite] Version 3.1.0

2005-01-21 Thread Jeff Edwards
To the unlearned laymen, 64bit CPU's mean that processing is performed 
twice as fast.

The assumption is that if an application is compiled for 64bit, then it 
will be operating faster.

Perhaps this is what Robert's assumption of 'taking advantage' was?
Jeff Edwards
On 22/01/2005, at 11:08 AM, D. Richard Hipp wrote:
On Fri, 2005-01-21 at 20:56 -0500, Robert L Cochran wrote:
Does this version take advantage of 64-bit cpu's like the AMD Athlon 
64?
I don't know.  What do you mean by "take advantage of"?
What does a 64-bit CPU do that you can't do with a 32-bit CPU?



Re: [sqlite] ANN: alpha DB sqlite util for MacOS X 10.3

2004-12-15 Thread Jeff Edwards
I have tried opening some existing sqlite3 files, but the browser shows  
nothing.  Perhaps i am doing something wrong?

it sounds like a great tool!
I am on 10.3.6 of OSX
Thanks
Jeff Edwards
On 14/12/2004, at 12:22 PM, Fernando Morgan wrote:
For MacOS X 10.3 users;
I was going to start to using sqlite in a project, but I need first to  
create a skeleton of a browser to add some of my data.

If someone wants to use it (disclaimer: version 0.1 software), it's  
here:

http://homepage.mac.com/fernandoluis/.cv/fernandoluis/Public/ 
SquidSQL.zip-link.zip (368k)

On starting, it open a file browser to open the db file. If this is  
cancel, it opens a Save File dialog and can create new db files. If  
this is also cancelled, well.. there's not much you can do besides  
Command-Q.

What is working: the table browser; it allows for viewing the data and  
to insert/update and delete rows in the table.

Table management (creating tables and dropping them) isn't working yet  
(some capability to create tables with text fields).

Done with SQLite 3.0.8.
Fernando



Re: [sqlite] Open Command broken under OSX

2004-09-06 Thread Jeff Edwards
With deepest respect Dr Hipp,  my original email did not read this way. 
 It said, "In other words, if the OS is macosx".

i do not know how this changed in the version published, but it has 
been changed.  In a previously email I outlined the problem under OSX 
which manifests itself in the terminal application, not just my build 
under x-code.  In that email I show the terminal application log of 
commands and responses.

BTW, OSX in most cases accepts either forward slashes or colans as the 
path delimiter.

Perhaps someone else can verify the problem under OSX.  The open 
command however does not work as expected.


> I also have another problem stemming from version 3. The open 
command seems
> not to work with the API.  In other words, if the OS is mac and I 
pass colans
> as the path delimiter, I end up getting a file name with slashes.  
if I pass
> a path name with forward slashes as the delimiter then I get an 
error. . .
> and sometimes I get no error returned, but still no file is created. 
 So it
> seems that the new way of opening (and creating where the file is 
not created
> immediately) has broken something.  Any ideas?
>

SQLite version 3.0 does not work with Mac OS-9 since nobody has ever 
submitted
drivers for it.  There is a file named "os_mac.c" in the distribution, 
but it
busted.  If you want to use OS-9 you'll need to stick with SQLite 
version 2.8.



Re: [sqlite] Re: Cursor naming conflict

2004-09-06 Thread Jeff Edwards
I did not mean to send this unfinished bit.
On 07/09/2004, at 10:50 AM, Jeff Edwards wrote:
I also labour under the 4D API plugin architechture which prefers that 
i do it in this.



Re: [sqlite] Re: Cursor naming conflict

2004-09-06 Thread Jeff Edwards
so you have a separate project to compile the windows library . . . .
Look . . I am not saying your way is wrong, but my way is less time 
consuming assuming I don't have a naming conflict.   If it is too much 
trouble for Dr Hipp to change the single name that is causing the 
problem, then so be it, but the arguments about obscure development 
environments and ignoring valid way to compile simply is not valid.  I 
also notice that there has been some confusion by Dr Hipp in mixing up 
the operating systems asserting that I am compiling for OS9 (I noticed 
that the email I sent to Dr Hipp and published by him on the list  has 
a portion of my words edited from macosx to Mac).

I also labour under the 4D API plugin architechture which prefers that 
i do it in this.

 . . . . . .  I am much more interested in getting the Open command bug 
getting fixed.

On 07/09/2004, at 10:34 AM, Will Leshner wrote:
On Sep 6, 2004, at 7:27 PM, Jeff Edwards wrote:
There is also the question of compiling for windows with the same 
source, but not the same library on the OSX machine.
Actually, I do use the same source. I just make a Windows library in 
CodeWarrior.





[sqlite] Re: Cursor naming conflict

2004-09-06 Thread Jeff Edwards
We agree with you with the scenario that you build the sqlite library 
and then link it into a project, however in our scenario, which does 
not appear to be obscure, we take the entire sqlite source code and 
directly compile it into our project.  Under this scenario, the 
internal headers are visible and do create conflicts.

Just to reiterate, we are using OSX, not OS9.  The problem appeared in 
both xcode and code warrior, and x code is not an obscure development 
framework.


No
The "Cursor" object in SQLite is an internal name.  It does not appear
anywhere in "sqlite.h" or "sqlite3.h".  Since the neither XCode nor 
Carbon
are required to compile SQLite, the definition of Cursor should not 
appear
in any of the files included by SQLite either.  So there should be no
conflicts.  If you are getting conflicts, I think the blame belongs to
the build environment, not SQLite.  I think it ill-advised to go around
altering names in SQLite in order to work around problems in obscure
build environments such as Code Warrior for Mac OS 9.



[sqlite] open command problem under OSX

2004-09-06 Thread Jeff Edwards
Just to expand on the problem of the open command that I outlined 
earlier,  I tested under a compiled version of sqlite (3.06) in the 
terminal application and passed the following:

[jbedwards:4DSqlite3/sqlite/bin] jeffedwa% ./sqlite3 
HD/Applications/jeff.db
SQLite version 3.0.6
Enter ".help" for instructions
sqlite> create table TEST(name varchar(30))
   ...> go
Unable to open database "HD/Applications/jeff.db": unable to open 
database file
[jbedwards:4DSqlite3/sqlite/bin] jeffedwa% ./sqlite3 
HD:Applications:jeff.db
SQLite version 3.0.6
Enter ".help" for instructions
sqlite> create table TEST(name varchar(30))
   ...> go
sqlite> .quit
[jbedwards:4DSqlite3/sqlite/bin] jeffedwa%

The file that was created was located in the bin directory and named 
"HD/Applications/jeff.db"
In other words the file name has forward slashes in it which were 
replaced from the colans.
If I have forward slashes in the path to the file I am wishing to 
create, then I get an error.
Something is definitely wrong with this part of the program


I also have another problem stemming from version 3.  The open command 
seems not to work with the API.  In other words, if the OS is macosx 
and I pass colans as the path delimiter, I end up getting a file name 
with slashes.  if I pass a path name with forward slashes as the 
delimiter then I get an error. . . and sometimes I get no error 
returned, but still no file is created.  So it seems that the new way 
of opening (and creating where the file is not created immediately) 
has broken something.  Any ideas?
Best regards,
Jeff Edwards


[sqlite] compiling sqlite3 under Code Warrior on OSX

2004-09-03 Thread Jeff Edwards
I am trying to compile sqlite version 3.6 on OSX with Code Warrior IDE 
version 5.1.1 build 1108 for a plugin to another database app.

Has anyone successfully done this yet?
I find that the pre-compiled headers contain declarations that are in 
the msl headers and not compatible.

With version 2.x I had no problem with except for some variable names 
which conflicted with the Carbon libraries.

Hoping someone else has had success with this.
Jeff Edwards


Re: [sqlite] Compute clauses

2004-03-05 Thread Jeff Edwards
I appreciate your response but perhaps you misunderstand me.

What I illustrated was a way to have totals after the detail.  The way 
to get this in Sybase is to use the "compute" clause.

I am after something similar in sqlite if it exists.

Thanks,

Jeff Edwards

On 05/03/2004, at 8:33 PM, Peter Pistorius wrote:

Yup.

	SELECT SUM(client_id) FORM client;

That will return the sum of client_id;

Regards,
PeterP


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[sqlite] Compute clauses

2004-03-05 Thread Jeff Edwards
In Sybase there is a transact SQL extension clause called "compute"

so if I was to write something like:

 select client_id, company from client where client_id <10 order by 
group_code compute sum(client_id)

I would get a result like this:

 client_id   company
 --- --
   1 Company 1
   2 Company 2
   3 Company 3
   4 Company 4
   5 Company 5
   6 Company 6
   7 Company 7
   8 Company 8
   9 Company 9
Compute Result:
 ---
  45
is there anything like this in sqllite which can give me a computed 
result ?

Thank you

Jeff Edwards

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[sqlite] Crystal Reports

2003-12-16 Thread Jeff Edwards
I am wondering if Crystal reports can be used with sqlite.

Can anyone give me a little knowledge about this.

Many thanks

Jeff Edwards

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]