This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 192069 - [70cat][generator] Database.yml file for JavaDB where database is not yet created is not generated properly.
Summary: [70cat][generator] Database.yml file for JavaDB where database is not yet cre...
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@ruby
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-17 18:22 UTC by esmithbss
Modified: 2011-01-28 20:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-11-17 18:22:26 UTC 
Product Version = NetBeans IDE Dev (Build 201011160001)
Operating System = Windows XP version 5.1 running on x86
Java; VM; Vendor = 1.6.0_20
Runtime = Java HotSpot(TM) Client VM 16.3-b01

When creating a new Rails project, on the database page of the wizard, if the user selects the lower half of the wizard and fills in the database particulars and selects the JavaDB database type and to use JDBC, then generates the application, the database.yml content that is generated is missing it's hostname declaration:

example:

development:
  adapter: jdbc
  driver: org.apache.derby.jdbc.ClientDriver
  url: jdbc:derby://localhost:1527/ActiveRecordSample_development
  user: test
  password: test


But if the database already exists, and the user uses the top 1/2 of the database wizard and selects an existing JavaDB database, the database.yml file which is generated has the hostname declaration

example:

development:
      host: localhost
      adapter: jdbc
      driver: org.apache.derby.jdbc.ClientDriver
      url: jdbc:derby://localhost:1527/ARSample_development
      username: test
      password: test


Without the hostname value, attempts to perform migrations appear to fail without error messages.