Vishal Kashyap wrote:
Dear All ,
I was wondering to upgrade from one SQLite version to other (refering 3.x).
Should I just replace the old sqlite3.exe file with the new one and
use the database as it is.
The database I have created dabase in 3.2.7 and want to move to 3.3.4.
How to go about
Jarl Friis wrote:
>
> How about just setting
> PRAGMA short_column_names = off
> PRAGMA full_column_names = on
> withing SQLColAttribute() and SQLColAttributes() and then, before
> returning from the function(s), setting it back to
> PRAGMA short_column_names = on
> PRAGMA full_column_names = off
At 7:05 PM -0500 3/12/06, [EMAIL PROTECTED] wrote:
Let me amplify this by pointing out that I have zero interest
in taking SQLite in the direction of The Third Manifesto. Those
who want to do so are welcomed - encouraged even - to fork the
tree and go off in their own direction. Just do not
Joe Wilson <[EMAIL PROTECTED]> wrote:
>
> If some people wish to pursue writing The Third Manifesto or some
> other SQL-derivative work, they should consider making a new
> SourceForge project of it (or whatever). Debating its merits here
> is offtopic to SQLite.
>
Let me amplify this by
"john.newby" <[EMAIL PROTECTED]> wrote:
> Hi, I sent this request yesterday from my other address but wasn't sure if
> anyone had received it as my other email address didn't receive it but both
> address are still receiving other peoples questions.
>
> I was wondering if anyone knew of any
"K. Haley" <[EMAIL PROTECTED]> wrote:
> >
> > But its worse than that, in that SQL isn't even consistent with itself
> > in how it treats nulls. With some kinds of operations or queries, it
> > treats every null being unique, and in other situations it treats them
> > all as being equal. No
Dear All ,
I was wondering to upgrade from one SQLite version to other (refering 3.x).
Should I just replace the old sqlite3.exe file with the new one and
use the database as it is.
The database I have created dabase in 3.2.7 and want to move to 3.3.4.
How to go about it.
--
With Best Regards,
Christian Werner <[EMAIL PROTECTED]> writes:
>> >> Further I wonder what's behind the decision to use
>> >> PRAGMA short_column_names = off
>> >> PRAGMA full_column_names = on
>> >>
>> >> When using short_column_names instead (which is default),
>> >> behaviour seems closer to standard Database
Sounds like a great idea to me.
I for one like SQLite just the way it is, warts and all. It serves my
purposes for a small, fast, efficient, flexible, and etc. Database. If
it starts "bloating up" to meet such esoteric purposes as the "third
manifesto", I will once again have to restart my
You can model NULL with the creation of a few more tables
listing the rows in which information is absent. But why should
you create more work for yourself? People find SQL to be useful in
its present form - NULLs and all. It is a fairly standard and well
known thing.
If some people wish to
Hi, I sent this request yesterday from my other address but wasn't sure if
anyone had received it as my other email address didn't receive it but both
address are still receiving other peoples questions.
I was wondering if anyone knew of any journals I could use for my University
dissertation on
Darren Duncan wrote:
>> I never understood that restriction. I read in the books: "since we
>> have defined things this ways from a formal point of view there's no
>> room for NULL". And my question is well, why don't you change the
>> definitions to augment the datatype sets with a special
12 matches
Mail list logo