> On Tue, Aug 17, 2010 at 10:46, Frans Bouma <[email protected]> wrote:
> > > 2) it's doing work that's unnecessary, as
> you're
> > testing work
> > > which
> > > can be done by a machine which doesn't make
mistakes.
> > >
> > > Did you read the part where I say this is autogenerated?
> > Generated by what exactly?
> >
> > A script.
>
>
> which grew on the ScriptTree? Or did you write it yourself?
> Another
> part of a chain, which can fail or contain bugs.
>
>
>
> It grew on the ScriptTree. You have no idea how much time I saved by
buying
> one of those :-D Also, did you know that script run logs are edible? They
> taste delicious with BBQ sauce.
only with color-coded paprika. ;)
> > Forgive me if I prefer IDEs that assist me with writing text to
> visual
> tools
> > like the one you sell. I am more productive with the former.
>
> 'you sell' ? Like the one you 'wrote' would have been more
> appropriate. I'm not selling anything, I only designed and wrote it
> from
> scratch. Like you did too. Oh wait...
>
> Point taken, wrote AND sell. Don't read too much into that.
>
> I'll go one step further and say that your product is probably better than
> 90% of the code generators.
thanks :) (still those 10%.. *grmbl* ;)).
> I'm only saying *I* don't use them.
I can imagine, it has to fit the way you want to work.
> > > WHAT? 8-O
> > > Automapping is model-first runtime code generation.
> >
> > oh? so, when you change some classes, it will... work
> on your
> > DB?
> > Oh, you have to trash the db, so how are you going to
> 'maintain'
> > things in
> > production then?
> >
> > Change scripts.
>
>
> yeah, those written by hand after carefully examining by hand
> what
> changes you made? Or by relying on diff tools which compare DDL SQL
> scripts
> however they always fall flat on their face when they have to deal
> with
> renames, type + renames, field moves, multiple fk + field changes,
> those?
>
> OK, how do you do it?
By recording the changes made in the model + mappings + meta-data.
Model + mappings drive meta-data (schema), and every change is recorded in a
command-based queueing system, which can be written to xml (yay!) into the
project file. This can then be used to produce change scripts which are
automatically created based on what you did with the model, so you don't
have to mess with 'what changed? did we miss a constraint somewhere?', which
can be tedious.
FB
>
> Diego
>
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en.
