[sqlite] Ann: Object Builder

2006-01-16 Thread Clay Dowling
To make it easier to build and maintain my CeaMuS product I wrote an automatic database object building tool. While it's intended to work with any programming language and database engine, CeaMuS was written using SQLite and C++. Object Builder follows in that tradition, with prebuilt

[sqlite] Slow sqlite3_step - more details.

2006-01-16 Thread Carl Jacobs
Hello, sorry for the lengthy email. I feel like I'm missing something, but I don't know what - is there anyone who could at least help me with a direction to search in. I'm using Windows XP Sp2, SQLite3.DLL V3.2.7. One of the tests which follows was repeated with bleeding edge SQLite3.DLL V3.3.1

Re: [sqlite] Problem executing SQLite 3.3.0 under MacOS

2006-01-16 Thread Robert L Cochran
You can search your Makefile to see if a module is set to compile an os.c. For example: [EMAIL PROTECTED] bld]$ egrep 'os' Makefile # This makefile is suppose to be configured automatically using the # same unless your are cross-compiling.) main.lo opcodes.lo os.lo os_unix.lo os_win.lo \

Re: [sqlite] Database design and SQLite

2006-01-16 Thread michael munson
You guys have been a lot of help. This is the idea I've gotten from the discussion we've had. Three tables: 1) Method table I did not mention this, because I pretty much already had the idea down. It will have the following columns: Where is a text entry that has stored some code

Re: [sqlite] Randomly ordering results

2006-01-16 Thread michael munson
So, I have to ask, is this the right way to implement such functionality? Is there a better, or more efficient way? Thanks in advance! -Clark Yes. It will be as random as your software random number generator. Which is to say, probably random enough.

[sqlite] Randomly ordering results

2006-01-16 Thread Clark Christensen
I'm creating an on-line exam, and I want to display a randomly-selected, randomly-ordered set of multiple-choice answers from the database for a given question (slide). CREATE TABLE MC_ANSWERS ( ANSWER_ID integer primary key, SLIDE_ID integer, ANSWER_TEXT text, IS_CORRECT

Re: [sqlite] Database design and SQLite

2006-01-16 Thread John Stanton
Marten makes good points. I would go further and suggest that you look at creating your own API and DB primitives for your application. Often you will find that trying to shoehorn general purpose tools into tightly specific applications is as much effort as rigorously defining the problem

Re: [sqlite] Database design and SQLite

2006-01-16 Thread Marten Feldtmann
Teg schrieb: Hello Marten, Monday, January 16, 2006, 2:14:59 PM, you wrote: To me duplicate entries or near duplicate entries in a table are a no-no. Sounds to me like you're talking about inserting the object multiple times in the same table each instance describing one "property" of the

Re[2]: [sqlite] Database design and SQLite

2006-01-16 Thread Teg
Hello Marten, Monday, January 16, 2006, 2:14:59 PM, you wrote: To me duplicate entries or near duplicate entries in a table are a no-no. Sounds to me like you're talking about inserting the object multiple times in the same table each instance describing one "property" of the object. What

Re: [sqlite] Database design and SQLite

2006-01-16 Thread Marten Feldtmann
Teg schrieb: Hello Marten, I wasn't suggesting one table for all object, I was suggesting a table for objects and a table for object properties. Using the object ID as a way to identify which properties belong to what objects in the properties table. The "Vertical" part was simply for the

Re: [sqlite] Database design and SQLite

2006-01-16 Thread Jim C. Nasby
On Mon, Jan 16, 2006 at 04:11:47AM -0600, michael munson wrote: > >At the worst that would be around 6 million columns on a property table. > >I've not used SQLite with tables that large before > >so I'm not sure if searching with 2 index values (name, and object its on) > >is going to be slow.

Re[2]: [sqlite] Database design and SQLite

2006-01-16 Thread Teg
Hello Marten, I wasn't suggesting one table for all object, I was suggesting a table for objects and a table for object properties. Using the object ID as a way to identify which properties belong to what objects in the properties table. The "Vertical" part was simply for the object properties

Re: [sqlite] CE locking -- review the code

2006-01-16 Thread Robert Simpson
- Original Message - From: "Simon Posnjak" <[EMAIL PROTECTED]> Robert Simpson wrote: I incorporated the locks into the latest CVS version of os_win.c and it's available here: http://sqlite.phxsoftware.com/os_win.c Would i be possible to post the whole src? (Taking the 3.3.1 src

Re: [sqlite] CE locking -- review the code

2006-01-16 Thread Simon Posnjak
Robert Simpson wrote: - Original Message - From: "Doug Nebeker" <[EMAIL PROTECTED]> Two comments: * This should only be used for Windows CE as-is. On Windows XP/2000/2003(?)/Terminal Services you should probably add "Global\" to the front of the mutex name so the lock is truly

Re: [sqlite] [PATCH] WinCE compilation

2006-01-16 Thread Simon Posnjak
[EMAIL PROTECTED] wrote: Simon Posnjak <[EMAIL PROTECTED]> wrote: Would it be possible if [Steve Lhomme's] port [to WinCE] and the sf port could be merged together in main line src tree? I have attempt to do this, but I have no way to test it. Anybody who is able to download the

Re: [sqlite] (resolved) problem using triggers to update primary key on FK type relationship

2006-01-16 Thread RCS Computers
I ended up trying this using SQLite 3.3.1 and it worked without a problem ( I was using 2.8.14). For those who may be interested, here is the test code that worked: CREATE TABLE [parent] ( [id] integer, [name] varchar (255) NOT NULL, PRIMARY KEY ([id]) ); --

Re: [sqlite] Database design and SQLite

2006-01-16 Thread Jay Sprenkle
On 1/16/06, michael munson <[EMAIL PROTECTED]> wrote: > Well, the main reasons I want to use a database as opposed to some other > type of arbitrary formatted file is real time access. > In the sense that I won't have to read the entire file into memory and can > just request objects as I need

Re: [sqlite] Database design and SQLite

2006-01-16 Thread Marten Feldtmann
Just some additional comments: The "vertical" approach (described by Teg) leads also to a very untypical relational database and if a pure sql administrator would look at it . Ok, but it works, but when using a vertical approach you have consider some points: * you have to throw away the

[sqlite] SQLite + uSQLite

2006-01-16 Thread Julien LEFORT
Hi, I'm using SQLite over a network with uSQLite. both are embedded on a PowerPC board with linux. The frequency of the cpu is 50MHz. I use SQLite 3.2.7 and uSQLite (sorry, couldn't find the version) I have written a simple C code to automatically fill some tables of my database, as I wanted to

Re: [sqlite] Database design and SQLite

2006-01-16 Thread Marten Feldtmann
Indeed it may be questionable to use SQLite for stuff like this, but its a very fast relational db library - and therefore it can be used as any other relational database to store objects. What is needed is very simple: you need a object-oriented relation database wrapper - either as a

Re: [sqlite] Database design and SQLite

2006-01-16 Thread michael munson
At the worst that would be around 6 million columns on a property table. I've not used SQLite with tables that large before so I'm not sure if searching with 2 index values (name, and object its on) is going to be slow. Heh, that should obviously read '6 million rows' . Sorry, its early.

Re: [sqlite] Database design and SQLite

2006-01-16 Thread michael munson
What about defining a table called 'properties'. It would have a key to link to the object and 'name' and 'value' column for each object property. You could have as many properties as desired for each object and they need not be the same for each object. That could be a solution, but at the upper