Yes i already wonder why this table creating looks so much different from the 
other table, because i needed many loops.This is the new 
version:db.execute("""CREATE TABLE IF NOT EXISTS TRAVELDAYS
       (TaskUID INTEGER PRIMARY KEY  AUTOINCREMENT,
       Day                     INT  NOT NULL,
       Value                   INT  NOT NULL);""")Is it enough that TaskUID is 
primary key or should (TaskUID, Day) be primary key for faster look up? 

     Hick Gunter <hick at scigames.at> schrieb am 14:56 Donnerstag, 5.M?rz 2015:


 With the query the OP described he is interested only in one day at a time so 
this won't hurt.

I am anticipating a question regarding variable column names in a query though.

-----Urspr?ngliche Nachricht-----
Von: R.Smith [mailto:rsmith at rsweb.co.za]
Gesendet: Donnerstag, 05. M?rz 2015 14:33
An: sqlite-users at mailinglists.sqlite.org
Betreff: Re: [sqlite] Bitfield in Sqlite3-Table



On 2015-03-05 03:00 PM, Oskar Schneider wrote:
> I just created for each day a seperate column is this worse than your 
> approach?
>
>
>? ? ? Hick Gunter <hick at scigames.at> schrieb am 8:01 Donnerstag, 5.M?rz 
>2015:
>
>
>

That's around 1000 columns, right?? Beware that SQLite has a standard upper 
limit in SQL column list length of 999 columns in queries, you can amend this 
with the API.

See:
https://www.sqlite.org/limits.html

_______________________________________________
sqlite-users mailing list
sqlite-users at mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


___________________________________________
 Gunter Hick
Software Engineer
Scientific Games International GmbH
FN 157284 a, HG Wien
Klitschgasse 2-4, A-1130 Vienna, Austria
Tel: +43 1 80100 0
E-Mail: hick at scigames.at

This communication (including any attachments) is intended for the use of the 
intended recipient(s) only and may contain information that is confidential, 
privileged or legally protected. Any unauthorized use or dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please immediately notify the sender by return e-mail message and 
delete all copies of the original communication. Thank you for your cooperation.


_______________________________________________
sqlite-users mailing list
sqlite-users at mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



Reply via email to