Re: [Tikiwiki-devel] DB Profiles

[Dennis H. <dh...@fi...>]

Since I wrote the profile feature, I'll explain how it's designed to work:

1) DB created manually
2) tiki-install.php runs the DB specific version of tiki.sql to create
objects and populate the established "defaults". The
db/profile/default-inserts.sql script is never actually run. but needs to
reflect the default values in tiki.sql for creating the profiles.
Essentially, the default inserts are subtracted from a database dump to
prevent re-running thme as part of the profiles.
3) The selected "profile" script is run after the tiki.sql script. It only
adds/updates the items that are different than the default install. If you
look at the "_default.prf" file (named that so it will always be at the
top of the list), it is empty. This is to keep things backwardly
compatible.

Doing it this way makes it easy to visually inspect the profiles and see
exactly what is changed from the Tiki default values. I didn't create the
BasicEnabled profile, so I can't address the specifics there, but the
errors that result from duplications are safe to ignore. If the profile
designer wants to change the value of a record that already has a default,
the statement should be an update or replace instead of an insert.

Hope that helps clarify things.

Dennis

> Because I probably won't be awake when the rest of you are online, I
> need to ask about DB profiles.
>
> I found an error in HEAD re db/profiles/BasicEnabled.prf - there are 4
> SQL statements that have ';' in them, which is confusing the tables
> creation. Not sure what the fix is, but thought I should let you know.
>
> The second problem I need to ask about - are default inserts officially
> being moved from db/tiki.sql to db/profile/default-inserts.sql??
>
> There is an error occurring under HEAD, where tiki_p_add_events is
> INSERTed  twice, causing an error. Not sure whether tiki.sql or
> default-inserts.sql should be modified to fix.