On 17 Apr 2014, at 1:21am, James K. Lowden wrote:
> Simon Slavin wrote:
>
>> If you really want to do it in the TABLE definition, use the SQLite
>> shell tool to '.dump' the table as a set of SQL commands, edit the
>> dump file to add that
On Wed, 16 Apr 2014 16:27:01 +0100
Simon Slavin wrote:
> If you really want to do it in the TABLE definition, use the SQLite
> shell tool to '.dump' the table as a set of SQL commands, edit the
> dump file to add that constraint, then use the SQLite tool to '.read'
> the
On 16 Apr 2014, at 4:02pm, Christoph P.U. Kukulies wrote:
> Am 16.04.2014 15:57, schrieb Richard Hipp:
>>
>> CREATE UNIQUE INDEX version_idx1 ON version(major,minor,date);
>
> Though this seems to work, could I achieve this also by a table constraint,
> like
Am 16.04.2014 15:57, schrieb Richard Hipp:
On Wed, Apr 16, 2014 at 9:46 AM, Christoph P.U. Kukulies
wrote:
Maybe been asked a hundred times but Im seeking for an elegant way to get
rid of duplicate rows which had been entered during development.
I have a database
On Wed, Apr 16, 2014 at 9:46 AM, Christoph P.U. Kukulies
wrote:
> Maybe been asked a hundred times but Im seeking for an elegant way to get
> rid of duplicate rows which had been entered during development.
> I have a database "versionen.sq3" having a table created by
>
>
Maybe been asked a hundred times but Im seeking for an elegant way to
get rid of duplicate rows which had been entered during development.
I have a database "versionen.sq3" having a table created by
CREATE TABLE version (major TEXT, minor TEST, date DATE)
Due to running across an iPython
6 matches
Mail list logo