Re: [sqlite] PRAGMA table_info oddness

Well, it's not the prettiest thing in the world, but it definitely works. Brilliant! Many thanks for your help, -Mike Ashmore On Jan 23, 2006, at 1:01 PM, Kurt Welgehausen wrote: Sorry, I didn't read your code carefully enough the first time. Your approach won't work because origin has no ex

Re: [sqlite] PRAGMA table_info oddness

Sorry, I didn't read your code carefully enough the first time. Your approach won't work because origin has no explicit type, and SQLite will not infer a type from the literal string; the unknown type defaults to numeric. As Dennis said, the problem is really with RoR, but you can work around it b

Re: [sqlite] PRAGMA table_info oddness

On Jan 22, 2006, at 7:43 PM, Kurt Welgehausen wrote: There's no string type in SQL. Go to and read section 2.1. Regards Okay, my previous message related to SQL syntax, so I suppose it's fair to point out that "string" isn't a SQL type. In fact, I shou

Re: [sqlite] PRAGMA table_info oddness

Mike Ashmore wrote: Hi folks, I'm trying to create a composite view from multiple database files, with an extra field for the origin of a particular record. A sample scenario: There's a table, "foo," which exists in two database files, 'a.db3' and 'b.db3'. Let's define it as: CREATE TAB

Re: [sqlite] PRAGMA table_info oddness

There's no string type in SQL. Go to and read section 2.1. Regards

[sqlite] PRAGMA table_info oddness

Hi folks, I'm trying to create a composite view from multiple database files, with an extra field for the origin of a particular record. A sample scenario: There's a table, "foo," which exists in two database files, 'a.db3' and 'b.db3'. Let's define it as: CREATE TABLE foo (f1 integer, f2