on 3/26/00 11:01 PM, David Soergel <[EMAIL PROTECTED]> wrote:
>> Management of the autogeneration stuff + extra
>> stuff would be a royal pain in the ass.
>
> My approach to this problem in Town was to encourage human changes
> only to a subclass of the main generated class. That way you can
> regenerate the superclass without wiping out your additions. If you
> want to change the behavior of a generated method, just override it
> in the subclass. This isn't perfect, of course, but works well
> enough for my purposes. :)
yea, i thought about this as well...(subclassing the generated
classes)...and i'm thinking that is probably the only decent solution, but
it does complicate things a bit...i'm still not 100% fond of generating java
code like that...
> It would be fairly easy to plug in an XML parser in place of the SQL
> one; but I figured that you have to have the SQL version of your
> schema on hand anyway. You're right that a better solution for the
> whole thing would be to generate the SQL from XML also... though the
> generator would have to know the quirks of different SQL variants for
> different DBs, and the XML stylesheet would have to accomodate all
> the options available in different SQLs; this could get very messy.
> Probably there are already XML stylesheets floating around that
> mirror SQL create table statements for some DBs anyway?
right right right...i understand what/why you are doing the things you are
doing in Town...I also agree, that XML may not be the right way to go here
(remember that XML does not solve all the problems out there)...;-)
it really sucks that none of us wants to just develop some killer end all
solution...i understand that it is really really hard to do, but it is SOOO
badly needed in the OS community...
i'm thinking that for now, i will just go back to hard coding Peers and
Map's...what a pain in the ass. ;-(
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
