Re: [sqlite] SQLite OLEDB provider for Linked Server

It looks like you get an activation code from their site, which can either be temporary or you can pay for a proper one. -- View this message in context: http://www.nabble.com/SQLite-OLEDB-provider-for-Linked-Server-tp24635046p24640083.html Sent from the SQLite mailing list archive at

Re: [sqlite] SQLite: Porting to another Operating system.

I'm new to SQLite. I would assume you would dump the tables to an external format and then load them into the new database. I can't however see where the documentation is for this kind of database management function. Anyone know where I should look, or do you have to download the SQLite3

Re: [sqlite] SQLite: Porting to another Operating system.

All you have to do is copy That's handy - I didn't realise that. However I suggest it's good practice to dump and reload in these kinds of situations. I don't yet know how SQLite works but I suspect a reload will get the physical data into a better shape and clear out deleted items etc. Do

Re: [sqlite] SQLite: Porting to another Operating system.

Thanks Donald. I can't see how you get to that page off the documentation menu but now I can go direct. I'm only familiar with DB2, Access Jet and Focus. In each case I would expect to reorganise the physical database on a regular basis - maybe daily or weekly. What's the best way of doing that

[sqlite] What is a Relation?

Just to kill time over coffee - what do you take the word to mean? I've just been reading a 1991 James Martin book on Object Orientation and he was using it to talk about links between entities. Chris Date was very specific that a relation was essentially a table. Mainly however, people seem to

Re: [sqlite] What is a Relation?

It's true that Codd and Date used the term 'relational' (They championed the N-ary Relational Model - others were around at the same time) but it's not easy to track the origin of the term in mathematics. Certainly the word implies joining things together. I guess the joining refers to fields

[sqlite] Denormalisation

I did a Computer Science MSc 30 years ago specialising in databases (the relational model was only in prototypes). Of course normalisation was well known, but what people would say is normalising is the easy part; the skill comes in 'collapsing'. More recently the term 'denormalise' has been used

Re: [sqlite] totally OT: debunking debunking SQL

Codd had his 'extended relational model' and I think Chris Date has got the Third Manifesto. Unfortunately people can't be satisfied they've invented something really, really simple and just feel proud, they want to become professors and write impenetrably clever papers that only their colleagues

[sqlite] Closure

As an aside, a principle of the relational model is that operations on relations should produce a relation. This caused a bit of a problem early on as if you perform a Project operation ie cut down the number of fields, you can finish up with 'duplicate' rows ie rows that can't be distinguished.

Re: [sqlite] Insert multiple entries in a single INSERT statement

Kees Nuyt wrote: > > > Insert one row at a time. > > > Presumably you can do this kind of thing: INSERT INTO Table2 ( [FieldX] ) SELECT FieldY FROM Table1; -- View this message in context:

Re: [sqlite] Question on converting objects into relational db

Bear in mind a relational database is designed around relations. It's not obvious what your 'data model' is but there is a suggestion it contains variable types of things. If you want to store variable things then many of the features of a relational database don't work. Often an object maps

Re: [sqlite] Question on converting objects into relational db

Simon Slavin-2 wrote: > > You can use property lists. > It's an interesting question as to what that gives you. It's clearly not a relation if you know how it was formed but - just thinking about it briefly - it may still behave as a relation as far as SQL is concerned. But it looks dodgy

[sqlite] SQLite Suitability for Shopping Cart

I am building a shopping cart application that calls a web service which provides lists of documents and the documents themselves. The user purchases document images. The application will load lists into a database, then build pages from the stored lists. The database will also keep track of

Re: [sqlite] SQLite Suitability for Shopping Cart

Thanks for that Sebastian. It does however surprise me. I believe Access Jet handles simultaneous activities. Indeed I've got a feeling it does row-locking rather than page-locking. It's odd that SQLite has such a limitation. Anyway, you've saved me a lot of heartache. -- View this message in

Re: [sqlite] SQLite Suitability for Shopping Cart

Fred Williams-5 wrote: > > no further need to ask and answer, "Will SQLite support > multi users? > Maybe it should be covered a bit more specifically on the SQLite site, bearing in mind that new people would naturally have the mindset that databases are for shared use normally. SQLite does

Re: [sqlite] normalization example(s)

You seem to be asking about four separate issues - normalisation, table creation, table loading, and SQLite syntax. The thing is I've just looked at your book's index and I can't imagine a better source of answers to your questions. Maybe you would like to post some specific cases here? --

Re: [sqlite] Sqlite reading all column data on selects.

In the relational model, the unit of access is a tuple so you would expect a DBMS to process all columns. Typically they also access in units of a page (although a tuple of course might extend across more than one page) The discussion seems to have moved onto selecting pages. Surely if you need

Re: [sqlite] normalization example(s)

Don't get carried away with keys, triggers and stuff like that at this point. For a start off your example is not normalised. You would have a person table and a food table but then you will need a person-food table as the relationship between person and food is many-to-many so you have to break

Re: [sqlite] feature request - field exclusion list in select list

This is altogether bad practice. You should always define what fields you want. Using Select * is just asking for trouble. To limit the number of fields that are accessible to a process/user/program, you should use a view. With a view you can of course then use Select * but that's not the point.

[sqlite] You can't

SQLite is a relational database. Relations are unordered sets so SQL, which SQLIte uses, doesn't have any operators to move backwards and forwards. With a relational database you should number your records in some way and then your application asks for the appropriate records by number, so if

Re: [sqlite] SQLite DB Structure

Firstly I'm not an SQLite expert but, now you know that, I would guess SQLite marks deleted records waiting until some clean-up process removes them and re-writes the active data. I would therefore look for some bit that is set. Try setting up a new database, adding records - taking a copy, then

Re: [sqlite] Table within a table??

Darren Duncan wrote: > > > Or at least it is in the version of the relational model > that allows non-scalar attribute values, but that is the one that Chris > Date et > al, as well as myself ascribe to. > > I didn't read this through but I recall Chris Date defining a relational

Re: [sqlite] Table within a table??

Darren Duncan wrote: > > Being that arrays *are* relations, you can use all the relational > operators on them. > Just to be totally clear - an array is not a relation. An array has fixed order of each dimension (eg columns and rows), and you address it by position. A relation is

Re: [sqlite] How to deal with non 'normilize-able' tables

What you are saying is you are holding information about items which have different characteristics. To represent these as relations you would have a product entity then you would have an attribute entity that would be like (product_id,attribute_id,attribute_name,attribute_value) eg: