This will show in sqlite_master like this:

type   name                                   tbl_name rootpage sql
---------------------------------------------------------------------------
index sqlite_autoindex_dataset_1 dataset  717

So, no SQL. Problem with this is that there is no way to see what fields
the index is on.
I suppose the only way round this is to look at the table create SQL.
Is this just the way it is?

RBS

On Tue, Dec 8, 2015 at 2:52 AM, Keith Medcalf <kmedcalf at dessus.com> wrote:

>
> create table dataset
> (
>    id integer not null,
>    timestamp integer not null,
>    data integer not null,
>    unique (id, timestamp)
> );
>
> > -----Original Message-----
> > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-
> > bounces at mailinglists.sqlite.org] On Behalf Of Andrew Stewart
> > Sent: Monday, 7 December, 2015 08:01
> > To: 'SQLite mailing list'
> > Subject: [sqlite] Making data unique
> >
> > Hi,
> >                 I have a table that consists of 3 elements:
> > ID - integer
> > Date/time - integer
> > Data - integer
> >                 A single ID can exist multiple times.
> >                 A single Date/time can exist multiple times.
> >                 An ID & Date/time combination is unique.
> >
> >                 What is the best way to ensure uniqueness in this table.
> >
> > Thanks,
> > Andrew Stewart
> > Software Designer
> >
> > Argus Controls
> > #101 - 18445 53 AVE
> > Surrey, BC  V3S 7A4
> >
> > t: 1-888-667-2091  ext : 108
> > t: 1-604-536-9100  ext : 108
> > f: 604-538-4728
> > w: www.arguscontrols.com<http://www.arguscontrols.com/>
> > e: astewart at arguscontrols.com<mailto:astewart at arguscontrols.com>
> >
> > Notice: This electronic transmission contains confidential information,
> > intended only for the person(s) named above. If you are not the intended
> > recipient, you are hereby notified that any disclosure, copying,
> > distribution, or any other use of this email is strictly prohibited. If
> > you have received this transmission by error, please notify us
> immediately
> > by return email and destroy the original transmission immediately and all
> > copies thereof.
> > _______________________________________________
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

Reply via email to