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 163686

Summary: [67cat] [db] Creating Rails For SQLite3 under JRuby, creates invalid database.yml
Product: ruby Reporter: esmithbss <esmithbss>
Component: RailsAssignee: issues@ruby <issues>
Status: NEW ---    
Severity: blocker    
Priority: P3    
Version: 6.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description esmithbss 2009-04-26 09:35:41 UTC 
[ BUILD # : 200904231401 ]
[ JDK VERSION : 1.6.* ]

When I create a new project and select to use SQLite3 in the Project
creation wizard, the database.yml file is invalid.

Example output:

development:
  adapter: jdbcmysql
  encoding: utf8
  reconnect: false
  database: db/development.sqlite3
  pool: 5
  username: root
  password:

Steps to Reproduce:
1) Have a Rails environment with the proper jdbc gems installed for
sqlite3 and mysql.
2) Create a new RoR Project.  Within the wizard, specify "SQLite3" as
the database type and specify that you want to access the database
using jdbc.
3) Once project is created, open the database.yml file.  It will look
like the above example (i.e.) which has a MySQL driver and a SQLite3
database.
Comment 1 ozydingo 2013-12-04 19:09:25 UTC 
This occurs as well when creating a new RoR project with existing sources. I have an existing project that uses mysql2 as the adapter, and when using "Create New Project" > "RoR app from existing sources", the database.yml file gets overwritten. I do not see a way to avert this other than to revert the database.yml file after creating the project in NB. This is both hacky and disruptive when getting others to use NB.