RE: [sqlite] Any advantages of "varchar()" over "text"?

2007-12-07 Thread Samuel R. Neff
-Original Message- From: P Kishor [mailto:[EMAIL PROTECTED] Sent: Friday, December 07, 2007 5:50 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Any advantages of "varchar()" over "text"? I may be wrong, but my understanding is that other than INTEGER PRIMARY

Re: [sqlite] Any advantages of "varchar()" over "text"?

2007-12-07 Thread Zbigniew Baniewski
On Fri, Dec 07, 2007 at 04:50:19PM -0600, P Kishor wrote: > I may be wrong, but my understanding is that other than INTEGER > PRIMARY KEY, SQLite doesn't give a rat's batuti about what you define Perhaps it's related to "closed relations" between SQLite and Tcl. Well, it's even more comfortable

Re: [sqlite] Any advantages of "varchar()" over "text"?

2007-12-07 Thread P Kishor
On 12/7/07, Zbigniew Baniewski <[EMAIL PROTECTED]> wrote: > We can define in, using SQLite, both "fixed max. width" VARCHAR() fields (I > know, in practice it can be crossed over), as well as "no limit" TEXT fields. > > So I would to ask: are there any benefits from using VARCHAR() and not TEXT? >

[sqlite] Any advantages of "varchar()" over "text"?

2007-12-07 Thread Zbigniew Baniewski
We can define in, using SQLite, both "fixed max. width" VARCHAR() fields (I know, in practice it can be crossed over), as well as "no limit" TEXT fields. So I would to ask: are there any benefits from using VARCHAR() and not TEXT? For example faster(?) data access - or just anything, that makes