not sure what you mean by databasemap below save("foo") is just going to
insert or update a row, it will not affect DatabaseMap.
You should not use the name attribute on <database> if the torque
objects are going to work with multiple databases.
john mcnally
On Tue, 2002-12-03 at 12:50, Simon Roberts wrote:
> Giddy,
>
> I've got a little problem that I'm hoping some of you can offer insight
> into. If it's a bug, or desired feature, I'm more than willing to
> add/contribute it, but I want to make sure I'm not barking up the wrong tree
> first.
>
> I have an appserver-type thing that we've just started to port to Torque,
> but are running up against a problem: the program needs to talk to N
> different databases, configured at runtime (all with the same schema).
>
> Is there *any* support for this kind of thing? I can see that the Ant
> tasks support explicit configuration, so it should be possible to drive it
> from ant.
>
> Also, if I configure a schema with <database name="node1"> and then call
> someRecord.save("node2") why is it that node1's databasemap is updated, not
> node2?
>
> Cheers, Simon
>
>
>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
