datasource

I have created a database named 'movie_db', set default schema to APP. Then created a sample table named 'USERS'. My connection to DB is as follows: <bean id="dataSource" class="org.springframework.jdbc.datasource.DriverManagerDataSource"> <property name="driverClassName" value="org.apache.derby.jdbc.ClientDriver"/> <property name="url" value="jdbc:derby://localhost:1527/movie_db"/> <property name="username" value="root"/> <property name="password" value="pass"/> </bean> Now I want to write some tests and try to execute the following query: SELECT * FROM USERS; What I get: java.sql

I am using Firebase database with a Json structure to manage users' comments. { "post-comments" : { "post-id-1" : { "comment-id-11" : { "author" : "user1", "text" : "Hello world", "uid" : "user-id-2" },.... } I would like to pull all the comments but excluding the current user's one. In SQL this will be translated into: Select * from post-comments where id !="user-id-2" I understand that Firebase database does not offer a way to excludes nodes based on the presence of a value (ie: user id != ...). Thus is there any alternative solutions to tackle this. Either by changing the Database structure

When I run the following snippet to connect to datasource to get the data out through queries : try { String driver = "com.microsoft.jdbc.sqlserver.SQLServerDriver"; Class.forName(driver); String Url = "jdbc:sqlserver://localhost:1433;databaseName=movies"; Connection connection = DriverManager.getConnection(Url,"sa", "xxxxxxx); // Context initContext = new InitialContext(); // Context envContext = (Context)initContext.lookup("java:comp/env"); // DataSource ds = (DataSource)envContext.lookup(""); // Connection connection = ds.getConnection(); String query_name = "select name from list where

I have java web application using Spring, Hibernate, Tomcat7 & MySql. I use Datasource for database operations. I am not very clear about what is the standard location to load the jar files ( Tomcat-jdbc.jar & Mysql-connector.jar ) from? It works if I keep BOTH the jars either in CATALINA_HOME/lib/ or webapps/myApp/WEB-INF/lib . But I was told to use only the Tomcat-jdbc from CATALINA_HOME/lib/ and mysql-connector.jar from /WEB-INF/lib/ , which gives a ClassNotFound Exception for Sql Driver . Can someone let me know which is the right location for these jars? <bean id="dataSource" class="org

I am using the PostgreSQL 9.1 JDBC4 driver (postgresql-9.1-902.jdbc4.jar) in a Java EE application deployed in JBoss 7. Can I assume that javax.sql.DataSource is thread-safe so that multiple threads can concurrently call the getConnection() method on it? javax.sql.DataSource itself is an interface, so it is a specific to the implentation if it is thread-safe or not. For the postgres sql driver, I recommend that you read Chapter 10. Using the Driver in a Multithreaded or a Servlet Environment from the official documentation: The PostgreSQL JDBC driver is thread safe. [...] Ian Roberts Typically

I'm using Spring Boot. I finally managed to setup two data sources, but now I'm facing another issue. with two data sources in place spring.jpa.hibernate.ddl-auto=create seems to stop working in my spring boot application, only spring.jpa.generate-ddl=true do the job now I can not manage to select the auto-creation strategy for each of the data sources. I would prefer to create the schema for data source one, and just use the created schema in second DB with data source two. Any body have idea how to resolve any of these issues? Note I don't want to completely throw away the auto-config if

We are using weblogic version 12C. Steps to reproduce the issue: - Create the datasource. Deploy the application to weblogic. Application works fine. Update the deployed ear with the new one. Application is not able to connect the datasource. Datasource not available in the JNDI tree. We need to create either a new datasource everytime or save the datasource setting again. Can someone please check and let me know if you know some solution for this? I had the same problem. Adding destroyMethod="" fixed it for me. Apparently if there is no destroyMethod, Spring tries to determine what the