That could be done by replacing the KEY definition in the AbstractSessionStore
public AbstractSessionStore(string Id)
{
sessionName = HashCodeProvider.GetIdentityHashCode(this).ToString() + Id;
}
On 10/11/06, Ron Grabowski (JIRA) wrote:
[
http://issues.apache.org/jira/browse/IBATISNE
+1. I understand your problem and I understand the proposed solution.But...At this time, you can achieve this using a HashMap:params.put("Customer", customer);params.put("DBTrash", dbTrash);
sqlMap.insert("statement", params)That said, I've been thinking iBATIS 3 should take a multiple parameter s
[
http://issues.apache.org/jira/browse/IBATISNET-185?page=comments#action_12441324
]
Ron Grabowski commented on IBATISNET-185:
-
Is there a reason why we can't move the SessionStore implementations into
IBatisNet.Common instead of duplic
Yeah, something like that..I hadn't thought at all about the syntax. :-)
Larry
On 10/10/06, Jeff Butler <[EMAIL PROTECTED]> wrote:
Hi Larry,
If I understand correctly what your suggesting, I'm thinking we could do
something like this:
1. Put a Map in ThreadLocal in the SqlMapClient
2. Add
Hi Larry,
If I understand correctly what your suggesting, I'm thinking we could do something like this:
1. Put a Map in ThreadLocal in the SqlMapClient
2. Add SqlMapCient methods like:
- clearThreadLocalMap()
- putThreadLocalData(String key, Object value)
3. Add some syntax to access these
Hi Richard,
It sounds like your taking the approach I labeled #3. Did you ever consider some kind of dynamic proxy? That's also been on my list to consider.There's obviously no good way to do this. Hopefully we can come up with a good idea by all thinking about it together. Thanks for partici
Not 10 different databases, ten different tables in the same database. Think header/detail records - but much more complex.
If you've never worked with an independant DBA group whose design philosophies are maintained solely at their own discretion - without needing to take the application needs
I guess I don't completely understand your issue. Do you have 10 different SqlMpas instantiated that call 10 different database and may share 1 domain object that needs to write to all of them? This souns extreme to me.
On 10/10/06, Jeff Butler <[EMAIL PROTECTED]> wrote:
It's not for display - it's
>>If your enterprise requires that you display audit data then what is it that is not part of the domain? Audit data is a nasty grey area. Auditing is a sort of shadow domain to the real application domain since it generally is interesting only to people who administer or control the application
[ http://issues.apache.org/jira/browse/IBATISNET-185?page=all ]
Gilles Bayon closed IBATISNET-185.
--
Resolution: Fixed
In SVN
> Allow custom ISessionStoreFactory
> -
>
> Key: IBATISNET-185
>
Jeff you took the words outta my mouth. Your idea gets a humble +1 from me.I've no idea about IBATIS internals but I think Jeff is proposing
something which would greatly increase the usability of the mapping.
I' m working on a team project where the persistence layer is my baby and I hate exposi
It's not for display - it's only required for update/insert.
Maybe I need to clarify what I mean by an "enterprise database". In our situation, this means "separate DBA and database design group - not under our control". So things like stored procedures, extra triggers, and table design changes
If your enterprise requires that you display audit data then what is it that is not part of the domain? It is domain relevant data. Just because it is shared among all database tables doesn't make it non-domain. For auditing i generally have a couple of different levels. One is "single generation"
IMO, it doesn't fit with the iBATIS philosophy.
There are as many solutions to this as there are projects, and making
a simple solution to this problem is not terribly likely.
I tend to put as much of that in the DAO (via threadlocal storage) or
in the database itself (via triggers, etc) as I ca
Hi All,
We have an issue that I believe is quite common with enterprise databases. Many (most) of the tables contain fields that are necessary for insert/update, but those fields do not really belong in our domain objects. These fields are often related to audit tracking in the tables (update t
[
http://issues.apache.org/jira/browse/IBATIS-324?page=comments#action_12441190 ]
Kjirsten Koka commented on IBATIS-324:
--
and report by hour/date # of times a statment was used.
>>
>>That can be added outside of iBATIS. You can inject a
Incorrect cacheModel example code
-
Key: IBATIS-355
URL: http://issues.apache.org/jira/browse/IBATIS-355
Project: iBatis for Java
Issue Type: Bug
Components: Documentation
Environment: iBATI
17 matches
Mail list logo
