| Summary | "content" module mysql script |
| Queue | Incubator |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | Twilek (at) gmx (dot) de |
| Created | 02/03/2009 (5996 days ago) |
| Due | |
| Updated | 02/04/2009 (5995 days ago) |
| Assigned | |
| Resolved | 02/04/2009 (5995 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
Patch ⇒ No
portability. Use the XML schemas to actually create the tables (using
MDB2_Schema directly, or the scripts from the Horde devtools package).
And if you're going to run bleeding edge dev code, you should be able
to cut-n-paste to create a new registry entry.
State ⇒ Feedback
(kronolith/lib/base.php defines the autoload paths for this to work).
Can you please provide a patch for your change instead of attaching
the entire file?
Priority ⇒ 1. Low
New Attachment: schema.mysql
Patch ⇒ Yes
Milestone ⇒
Summary ⇒ "content" module mysql script
Type ⇒ Enhancement
State ⇒ New
Queue ⇒ Incubator
with mysql (it was just the autoincrement needing to be auto_increment).
Would you be so kind to add the "content" package to the registry or
at least document the right code somewhere in the wiki or in chora how
to do that. It took me quite some time to get it right (you can´t edit
entries in git kronolith without a proper "content" installation)