Hello all.
The RIFE/Crud Getting started page
(http://rifers.org/wiki/display/RIFECRUD/Getting+started) states:
"...[Automatic table creation] is not mandatory and that RIFE's persistence
layer can map the properties to existing tables."
How do you do that?
If I take out the CreateCrudStructureParticipant participant, I get a message
that says:
The site 'crud:com.tx.app.data.MyData' declares an unsupported site processor
identifier 'crud'. Since I am using Derby at the moment, I have the option of
just blowing away the files. But it won't always be so.
Another small issue, I have a byte [] property called thumbnail, to which I
apply:
addConstraint(new ConstrainedProperty("thumbnail")
.notNull(true)
.file(true)
.listed(true)
.mimeType(MimeType.IMAGE_JPEG)
.contentAttribute("width", 150));
...But CRUD doesn't seem to understand that this is a file upload, I just get
a text field. Is there something else I need to add?
On another note, I saw in previous posts where you were trying to figure out
how to handle schema changes. Have you thought about mimiking the
ActiveRecord Migration idea:
http://wiki.rubyonrails.com/rails/pages/UsingMigrations ?
I'm sure you have, just thought I would throw it out there.
MetaData classes could have migrateForward/migrateBackward methods which
contain only the most recent deltas. And some constraint-like mechanism could
define the table changes. For this to be effective, you'd have to be using
version control, and probably tagging for every schema change. Backing up
would be painful, but mostly we'd be moving forward. There is also the issue
of deciding when/how to run the migrations, the RAILs approach is manual.
Maybe have a way of checking the meta data against the database, and
attempting migrateForward is a difference is detected?
Anyway, just a thought...
- John
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
