I am attempting to port a legacy DB and application to WebVelocity
using MySQL, but I am experiencing some strange behavior. I don't
know where to look.
Every read of the DB schema results in messages like these being
dumped to the Transcript:
Cannot find type timestamp using integer instead.
Cannot find type date using integer instead.
Cannot find type text using integer instead.
So, any table that has a column of type timestamp, date, or text
results in these messages.
Also, it seems that access to anything schema related in the browser
causes Velocity to re-read the full schema (very slow indeed). For
instance, browsing to any of the built-in views (ListUI, EditUI,
ViewUI), browsing to a model class, browsing the schema class, etc.
all cause a re-read of the schema. Nothing is cached.
Another issue is that after creating the model classes from my schema,
I don't have any tableFor<NAME>: methods generated in the schema
class.
Any help is certainly appreciated.
--
Jason Rogers
"I am crucified with Christ: nevertheless I live;
yet not I, but Christ liveth in me: and the life
which I now live in the flesh I live by the faith of
the Son of God, who loved me, and gave
himself for me."
Galatians 2:20
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
