hi,
would anybody happen to know how to recreate (drop, then
create) a database with stripersist?
further, do you know how to drop/create a specific table
within a database?
i'm using hibernate with stripersist.
thank you for you help,
lev
On 07/13/2010 08:22 AM, Lev wrote:
hi,
would anybody happen to know how to recreate (drop, then
create) a database with stripersist?
further, do you know how to drop/create a specific table
within a database?
i'm using hibernate with stripersist.
Do you want to change the structure of
On 13-07-2010 at 12:01, Thomas Menke wrote:
On 07/13/2010 08:22 AM, Lev wrote:
would anybody happen to know how to recreate (drop, then
create) a database with stripersist?
further, do you know how to drop/create a specific table
within a database?
i'm using hibernate with
Yes, that's correct. Yet another reason to be disciplined when it comes to
automated testing :)
Op 13 jul. 2010 om 20:23 heeft Aaron Stromas passog...@gmail.com het volgende
geschreven:
Thanks for the suggestion. I wasn't aware of if before. From what I was able
to gather, if I do change
Testing is not the worrying bit. What if changing the strategy indeed
affects something else? It would have to be recoded. Is there no way of
avoiding the global change, to restricting its scope?
On 13 July 2010 14:36, Levi Hoogenberg levihoogenb...@gmail.com wrote:
Yes, that's correct. Yet
Ah, I hadn't thought of that. Indeed, having to change code would be disastrous
;)
Seriously, though: the change is global, so if you really, really want to avoid
changing the population strategy you'll have to use a workaround. One thing I
can think of (and there probably are other ways as
I wanted to be sure I'm not busting out of framework if there is a way not
having to do so. Thanks again,
-a
On 13 July 2010 15:03, Levi Hoogenberg levihoogenb...@gmail.com wrote:
Ah, I hadn't thought of that. Indeed, having to change code would be
disastrous ;)
Seriously, though: the
Aaron,
Freddy Daoud mentions in his book on pg 183 why
BeanFirstPopulationStrategy isn't the default...
i.e. even though it is often the preferred strategy in that it uses
values set in the action bean first and if that fails uses the request
parameters... it wasn't introduced until 1.4 and
I, actually, will be trying out changing the default strategy. The
application is still small enough that even if something breaks, it can be
mended without too much pain. Thanks.
-a
On 13 July 2010 16:08, Nikolaos Giannopoulos nikol...@brightminds.orgwrote:
Aaron,
Freddy Daoud mentions in
On Tue, Jul 13, 2010 at 1:31 PM, Oscar Westra van Holthe - Kind
os...@westravanholthe.nl wrote:
On 13-07-2010 at 12:01, Thomas Menke wrote:
On 07/13/2010 08:22 AM, Lev wrote:
would anybody happen to know how to recreate (drop, then
create) a database with stripersist?
further, do you
You could run each test inside a transaction - just rollback after each test
[method] and you're golden.
On Tue, Jul 13, 2010 at 11:01 PM, Lev d...@plektos.com wrote:
On Tue, Jul 13, 2010 at 1:31 PM, Oscar Westra van Holthe - Kind
os...@westravanholthe.nl wrote:
On 13-07-2010 at 12:01,
Lev,
I pretty much do the same thing you are asking about... which got
tiresome after a while when the tables changed significantly... so the
top of my tests run a method to drop the appropriate tables in a
@BeforeClass method.
Just put the following code into a method and call it from your
12 matches
Mail list logo
