17 09:35
> > To: sqlite-users@mailinglists.sqlite.org
> > Subject: [sqlite] change ORDER BY slowly
> >
> > Hi,
> >
> > I have a phone book (bm_ppal), 726.000 rows, 10 columns
> >
> > This phone book have this columns
> > Name Declared Type Type
s@mailinglists.sqlite.org
> Subject: [sqlite] change ORDER BY slowly
>
> Hi,
>
> I have a phone book (bm_ppal), 726.000 rows, 10 columns
>
> This phone book have this columns
> Name Declared Type Type Size
> nbmId INTEGER INTEGER
> nbmCodigo VARCHAR (6) VARCHAR 6
RIMARY KEY (rowid=?)
-Original Message-
From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
Behalf Of MONSTRUO Hugo González
Sent: Monday, March 27, 2017 11:35 AM
To: sqlite-users@mailinglists.sqlite.org
Subject: [sqlite] change ORDER BY slowly
Hi,
I have a
On 27 Mar 2017, at 4:35pm, MONSTRUO Hugo González
wrote:
> nbmCodigo VARCHAR (6) VARCHAR 6
I wanted to note that SQLite completely ignores VARCHAR and any size limits.
As far as SQLite is concerned, all those fields are TEXT fields and can contain
any number of
Hi,
I have a phone book (bm_ppal), 726.000 rows, 10 columns
This phone book have this columns
Name Declared Type Type Size
nbmId INTEGER INTEGER
nbmCodigo VARCHAR (6) VARCHAR 6
abmNombre VARCHAR (320) VARCHAR 320
abmNombrePlano VARCHAR (320) VARCHAR 320
nbmCiudad INTEGER INTEGER
nbmTelefono
5 matches
Mail list logo