Krzysztof Swietlinski wrote:
> This is how DB behave. You can never be sure in what
> order elements are retrieved. There are solutions for
> this problem (at least using pure SQL), but they tend
> to be cumbersome. In my experience it's always better
> to arrange business logic, so it doesn't depend on
> order or the order can be achieved by a simple ORDER
> BY clause.
I know thats how DB's behave, this is however not how
Vector usually behaves. One could argue that Vector as
used by castor doesn't fullfill its contract with Client
application.
> This is how DB behave. You can never be sure in what
> order elements are retrieved. There are solutions for
> this problem (at least using pure SQL), but they tend
> to be cumbersome. In my experience it's always better
> to arrange business logic, so it doesn't depend on
> order or the order can be achieved by a simple ORDER
> BY clause.
I know thats how DB's behave, this is however not how
Vector usually behaves. One could argue that Vector as
used by castor doesn't fullfill its contract with Client
application.
Kind Regards
Jan H. Hansen
