On Wed, Feb 2, 2011 at 10:11 AM, Siddharth Srivastava (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989731#comment-12989731 > ] > > Siddharth Srivastava commented on DERBY-4907: > --------------------------------------------- > > The code changes done seem to resolve this issue. I have created a patch > using Eclipse (Team->create Patch). But when I upload it on jira using: > MoreActions->Attach File, I get Unknown error occurred uploading file. > > > >> EmbeddedXADataSource with ;create=true attribute set in setDatabaseName >> fails with java.sql.SQLException: Database not available >> -------------------------------------------------------------------------------------------------------------------------------- >> >> Key: DERBY-4907 >> URL: https://issues.apache.org/jira/browse/DERBY-4907 >> Project: Derby >> Issue Type: Bug >> Components: JDBC >> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, >> 10.6.2.1 >> Reporter: Kathey Marsden >> Assignee: Siddharth Srivastava >> Priority: Minor >> >> Setting the ;create=true attribute in setDatabaseName with >> EmbededXADataSource and EmbeddedXADataSource40 fails with >> $ java TestDerbyCreate >> Exception in thread "main" java.sql.SQLException: Database not available >> at >> org.apache.derby.jdbc.EmbeddedXADataSource.setupResourceAdapter(Embe >> dedXADataSource.java:175) >> at >> org.apache.derby.jdbc.EmbeddedXADataSource.getXAConnection(EmbeddedX >> DataSource.java:101) >> at TestDerbyCreate.main(TestDerbyCreate.java:18) >> >> using the create attributie in databaseName works fine with >> EmbeddedDataSource. >> Using setCreateDatabase("create") with EmbeddedXADataSource is a good work >> around and I think generally preferable. >> import java.sql.*; >> import javax.sql.*; >> public class TestDerbyCreate >> { >> public static void main(String[] args) throws Throwable >> { >> org.apache.derby.jdbc.EmbeddedXADataSource ds = >> new >> org.apache.derby.jdbc.EmbeddedXADataSource(); >> ds.setDatabaseName("TestDB;create=true"); >> ds.setUser("dbuser1"); >> ds.setPassword("dbpwd1"); >> PooledConnection pooledConn = ds.getXAConnection(); >> Connection conn = pooledConn.getConnection(); >> System.out.println("Database product: " + >> conn.getMetaData().getDatabaseProductName()); >> System.out.println("Database version: " + >> conn.getMetaData().getDatabaseProductVersion()); >> System.out.println("Driver name: " + >> conn.getMetaData().getDriverName()); >> System.out.println("Driver version: " + >> conn.getMetaData().getDriverVersion()); >> System.out.println("JDBC driver major ve > > -- > This message is automatically generated by JIRA. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
That's odd. I use eclipse, but I normally build and create patches outside of eclipse...(old habits). Do you have subversion installed as well, or only subclipse? If you have subversion also, you could do an svn diff at the top of the tree (trunk) and redirect to a file, then compare with the patch created by sub/eclipse... Re upload trouble, even if the patch created by eclipse is unusual in some way I'd not expect this result. Jira was just upgraded (yesterday, I think), perhaps it's got file upload trouble? Try to upload some innocent text file - you can always delete it again... HTH. Myrna
