Hello
I need to write an application to manage appointments. Most of them
are recurrent, with no end-date, while others are one-shots, and the
user must be able to schedule reccurent appointments but be able to
tweak some of them if need be.
To investigate whether I need to bother keeping two tables (one-shots,
recurrent, and merge both to display the actual appointment book), I'd
like to see how SQLite performs if I use the brute-force approach,
which is pre-creating appointments till eg. 2100. Not very smart, but
if it works well...
Do I need to loop through this, or is there a command that lets me use
a single INSERT using something like pseudo "START_DATE, END_DATE,
FREQUENCY_EVERY_MONDAY_AT_10AM", etc?
======
sqlite> create table agenda (id INTEGER PRIMARY KEY, date VARCHAR,
label VARCHAR
);
sqlite> insert into agenda (id,date,label) values (NULL,"20080902",
"Test");
sqlite> commit;
======
Thank you.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
