Parent Directory | Revision Log
Links to HEAD: | (view) (annotate) |
Sticky Revision: |
make ldap2model use JiftyModelCreator and minor tweaks all over the place
make pod pass test :-)
since we can't really reliably tell which columns should database have by just looking into schema, we need to enable users to specify additional classes to mix them in. Also generate really nice perl code now, which even works! YAY!
- don't insert single-value comment (corrupts model) - comment out filter for arrays (doesn't work yet) - create array of values for test data (which get squashed into scalar by Jifty currently)
added pod usage, debug won't touch filesystem any more
added command-line options and ability to pull schema from LDAP server Example usage is now: ./bin/ldap2model.pl --model hrEduOrg to pull hrEduOrg objectClass from LDAP server or ./bin/ldap2model.pl --model hrEduOrg --path data/all.ldif to use ldif instead (server is prefered in on-line situations)
create tests with required columns (must from LDAP) and accessor name if not included (by default, it's id)
create Jifty model skeleton from LDAP schema - create all attributes from LDAP - generate accessor for aliases in LDAP
minimal LDAP schema to Jifty model generator We are not using dynamic class generation (a.k.a. Jifty magic) here because models generated this way will probably have to be manually edited anyway.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
ViewVC Help | |
Powered by ViewVC 1.1.26 |