|
|
|
|
I have a utility that gets an sql connection from another library. Is there a "right" way to create an SqlSessionFactory based on a provided (by api) sql connection pool and not rely on db loging from within mybatis OR by providing a sql Driver on the other hand?
--
You received this message because you are subscribed to the Google Groups "mybatis-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/mybatis-user/eb234eb2-b2bd-4c85-8c1c-6c3f60192109%40googlegroups.com.
|
|
|
Correct. You simply supply a java.sql.Connection, however you choose to obtain one. You are not restricted, so yes, you *may* skip data source creation in the environment, if you wish. And no, nothing is mandating that you handle connection pooling. For example, if this is a one time requirement, you don't need a connection pool at all, simply create a Connection using DriverManager.getConnection(). On the other hand, if you running an environment that already has connection pools (e.g., Tomcat or JBoss), then you can simply obtain a connection from those existing pools.
--
You received this message because you are subscribed to the Google Groups "mybatis-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/mybatis-user/em66d2f74c-999f-4553-8db3-2bbb43ab7648%40asus.
|
|
|
That won't work for me. I have table with dynamic names, I need to run the code when I provide the sql connection my self since the login for some db's on customer site are complex using kerberos anf other means of authentications. So - I have to find a lib which has java api that I can interact with.
Regards,
Yair
Correct. You simply supply a java.sql.Connection, however you choose to obtain one. You are not restricted, so yes, you *may* skip data source creation in the environment, if you wish. And no, nothing is mandating that you handle connection pooling. For example, if this is a one time requirement, you don't need a connection pool at all, simply create a Connection using DriverManager.getConnection(). On the other hand, if you running an environment that already has connection pools (e.g., Tomcat or JBoss), then you can simply obtain a connection from those existing pools.
You received this message because you are subscribed to a topic in the Google Groups "mybatis-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mybatis-user/OPCXVnHFyEE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/mybatis-user/em66d2f74c-999f-4553-8db3-2bbb43ab7648%40asus.
--
You received this message because you are subscribed to the Google Groups "mybatis-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/mybatis-user/CAMWFgdgkjLTapF0cyyZqOJaZchr_xyfnjZJeKnpbJBHjRYo6gA%40mail.gmail.com.
|
|
Locked
