[sqlite] Select Into not working

I am attempting to copy records from one table to another. The following statement is what i see everywhere when I google how to do this, yet it does not work. I am using the following: Select field1, field2 into {newly created table} from {existing table with lotsa records} I get an error Error

Re: [sqlite] Select Into not working

On 18 Apr 2011, at 4:45am, mhnSqlite wrote: > I am attempting to copy records from one table to another using the syntax : > Select field1, field2 into {empty table just created} from {existing table > with a bunch of records} INSERT INTO newTable SELECT this,that FROM oldTable

[sqlite] Select Into not working

I am attempting to copy records from one table to another using the syntax : Select field1, field2 into {empty table just created} from {existing table with a bunch of records} I get an error "Error near "Into" The destination table has only field1 and field2 which are also in the source table.

Re: [sqlite] Select Into not working

On 18 Apr 2011, at 4:40am, mhnSqlite wrote: > > [nothing] > -- You cannot post attachments to this list. You must type your message as text. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] Select Into not working

-- View this message in context: http://old.nabble.com/Select-Into-not-working-tp31420529p31420529.html Sent from the SQLite mailing list archive at Nabble.com. ___ sqlite-users mailing list sqlite-users@sqlite.org

[sqlite] Attach Database---Insert Into no work

I have a need to create a new SQL Lite database. My only means to do so is with a utility "WinSQL". It connects to any existing database using a DSN set up in the ODBC administrator that is in the control panel. My work flow that I have worked out dies when attempting to copy records from an

Re: [sqlite] How to Use an Apostrophe in a Text Field?

On 17 Apr 2011, at 11:54pm, Alan Holbrook wrote: > I'm using SQLite with VBE2008. I've defined a table with a number of text > fields in it. If the information I want to write to the database contains > an embedded apostrophe, the program throws an error. That is, if I set > textfield1 to

Re: [sqlite] 'integer'

On 18 Apr 2011, at 1:53am, Roger Binns wrote: > Your complaints are really that SQLite doesn't function exactly how you are > used to. Note that it does do exactly what you tell it - the behaviour is > not random. It's probably worth Stefan reading the SQL specification. Stefan, please read

Re: [sqlite] 'integer'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2011 04:43 PM, Stefan Keller wrote: > I clearly prefer 'weakly typed' (or even type-less) over "dynamically > typed" (mentioned in http://www.sqlite.org/datatype3.html ). The irony is that SQLite is more strongly typed in my opinion. If you

Re: [sqlite] 'integer'

Sorry for those brutally honest words - and yes, datastore is not well defined. But look at how homepage introduces SQLite: a "serverless, ... SQL database engine". As said, I believe SQLite could avoid traps by declaring more clearly what it is and what it is *not*. Wikipedia says: it is "an

Re: [sqlite] How to Use an Apostrophe in a Text Field?

On Sun, Apr 17, 2011 at 3:54 PM, Alan Holbrook wrote: > I'm using SQLite with VBE2008.  I've defined a table with a number of text > fields in it.  If the information I want to write to the database contains > an embedded apostrophe, the program throws an error.  That is,

Re: [sqlite] How to Use an Apostrophe in a Text Field?

On Apr 17, 2011, at 5:54 PM, Alan Holbrook wrote: > I'm using SQLite with VBE2008. I've defined a table with a number of text > fields in it. If the information I want to write to the database contains > an embedded apostrophe, the program throws an error. That

[sqlite] How to Use an Apostrophe in a Text Field?

I'm using SQLite with VBE2008. I've defined a table with a number of text fields in it. If the information I want to write to the database contains an embedded apostrophe, the program throws an error. That is, if I set textfield1 to *Going Down the Road Feeling Bad*, the data gets written

Re: [sqlite] Newbie question

Lucas Cotta wrote: > Are primary keys and foreign keys indexes by default? Or do we have to set > them as indexes? An index is automatically created to implement PRIMARY KEY and UNIQUE constraints. No indexes are automatically created for foreign key constraints. Columns

Re: [sqlite] sqlite-3.7.6.1 coredump/hang

To wrap this up: The bugfix in 3.7.6.2 seems to solve this issue. Thanks for the help, Thomas On Fri, Apr 15, 2011 at 07:27:57AM +0200, Thomas Klausner wrote: > Hi! > > With 3.7.6 and 3.7.6.1 on NetBSD-5.99.49/amd64, a program I'm using > started dumping core. > > The sequence it is using is

[sqlite] Newbie question

Hi! Are primary keys and foreign keys indexes by default? Or do we have to set them as indexes? Thanks ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] 'integer'

Stefan, > SQLite should'nt be called a "SQL database" (as e.g. touted on its homepage). > Instead it should clearly declare itself as an "In-memory SQL > Datastore" or a "Data container with SQL capabilities". This is quite serious allegations. Making them you should explain what they are based

Re: [sqlite] Persistently setting certain PRAGMAs (foreign_keys, recursive_triggers)

On Sun, Apr 17, 2011 at 7:23 PM, Nico Williams wrote: > Yes. In fact, I've considered storing all the startup statements in a > table such that I could tell advanced users how to trivially find how > to setup their DBs. Of course, since there's no eval(), and that's a >

Re: [sqlite] Persistently setting certain PRAGMAs (foreign_keys, recursive_triggers)

On Sun, Apr 17, 2011 at 11:44 AM, Petite Abeille wrote: > On Apr 17, 2011, at 6:33 PM, Nico Williams wrote: >> Now, it's true that that's expected, but if all the application >> "business" logic can be encoded in table constraints, indexes and >> triggers, then it ought

[sqlite] Problem installing sw-sso package based on sqlite because of schema version

Hello, I'm trying to install sw-sso package on my Debian server and this package use sqlite. The installation fails because of the schema version : DB file already exists. Let's check for upgrade DB update failed (Downgrade is not supported (8 -> 7).). See log file for detailed output. Whe I

Re: [sqlite] Persistently setting certain PRAGMAs (foreign_keys, recursive_triggers)

On Apr 17, 2011, at 6:33 PM, Nico Williams wrote: > Now, it's true that that's expected, but if all the application > "business" logic can be encoded in table constraints, indexes and > triggers, then it ought to be possible to make it safe to access via > the shell, and _that_'s what I'm

Re: [sqlite] Persistently setting certain PRAGMAs (foreign_keys, recursive_triggers)

On Sun, Apr 17, 2011 at 3:36 AM, Kees Nuyt wrote: >> Is there any way to persistently set certain PRAGMAs, so that they >> need not be set every time a DB handle is opened? > > Many PRAGMA default valuess can be influenced using compiler flags > SQLITE_DEFAULT_* . I was mildly

Re: [sqlite] 'integer'

I'm new around here - exactly what element of SQLite precludes it from being a database? On 17/04/2011 13:12, Stefan Keller wrote: > Michael and Jay are right about the subtleties on how SQlite > interprets what is a data type, a primary key and a database schema > and it's ACID implementation

Re: [sqlite] 'integer'

Michael and Jay are right about the subtleties on how SQlite interprets what is a data type, a primary key and a database schema and it's ACID implementation in general. To me, the main reason - and remedy - of this FAQ is that SQlite should'nt be called a "SQL database" (as e.g. touted on its

Re: [sqlite] 'integer'

Seems to behave OK for me on 3.7.5 on Windows. What version are you using on what OS with what compile flags? You also "said" it didn't work but you didnt' actually what what you did. Like this... SQLite version 3.7.5 Enter ".help" for instructions Enter SQL statements terminated with a ";"

Re: [sqlite] Persistently setting certain PRAGMAs (foreign_keys, recursive_triggers)

On Sun, 17 Apr 2011 01:11:51 -0500, Nico Williams wrote: > Is there any way to persistently set certain PRAGMAs, so that they > need not be set every time a DB handle is opened? Many PRAGMA default valuess can be influenced using compiler flags SQLITE_DEFAULT_* . See the

[sqlite] Persistently setting certain PRAGMAs (foreign_keys, recursive_triggers)

Is there any way to persistently set certain PRAGMAs, so that they need not be set every time a DB handle is opened? Thanks, Nico -- ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users