On Vie, 11 de Febrero de 2005, 10:01, Gregor J. Rothfuss dijo:
> Antonio Gallardo wrote:
>
>> Can you post some of them? I cannot wait to see them! ;-)
>
> here is the first one:
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=33523
>
> take a look at the code to see what i mean when i say it
Antonio Gallardo wrote:
Can you post some of them? I cannot wait to see them! ;-)
here is the first one:
http://issues.apache.org/bugzilla/show_bug.cgi?id=33523
take a look at the code to see what i mean when i say it should not be
used, and that's just the relatively harmless databaseReader..
i
On Jue, 10 de Febrero de 2005, 16:49, Gregor J. Rothfuss dijo:
> i disagree violently :)
lol.
> we are currently refactoring an application that is infested with them,
> and we found several bugs. let me see about releasing those fixes.
Can you post some of them? I cannot wait to see them! ;-)
Antonio Gallardo wrote:
Don't agree. It is posible to do with them a lot of work. They are stable
and not buggy. The reasons to I don't recommend them is because the
maintenance of the system is more complicated. That is all! With O/R
mapping it is more easy the later maintenance work.
For the reco
On Jue, 10 de Febrero de 2005, 11:30, WHIRLYCOTT dijo:
> My view on this particular matter may go against the grain here, but I
> think that both the modular db actions and the sql transformers should
> not, in general, be used.
>
> Your work with the modular db actions and the sql transformer will
WHIRLYCOTT wrote:
My view on this particular matter may go against the grain here, but I
think that both the modular db actions and the sql transformers should
not, in general, be used.
Your work with the modular db actions and the sql transformer will not
be portable since they are tightly cou
My view on this particular matter may go against the grain here, but I
think that both the modular db actions and the sql transformers should
not, in general, be used.
Your work with the modular db actions and the sql transformer will not
be portable since they are tightly coupled to Cocoon. T
You may consider using an O/R mapping framework like Hibernate or OJB in
combination with flowscript and cforms.
I tried the modular DB actions long time ago, and then switched to
Hibernate. Never thought about switching back.
Your flowscript code will contain these steps:
- populate bean from t
On Jue, 10 de Febrero de 2005, 7:56, Kim Toms dijo:
> I have cocoon and can create pages reflecting queries in the database.
>
> I recently got enough working to be able to change the database.
>
> The question is, what is the best procedure to perform SQL "Update" or
> "Insert" type statements?
>
