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.
| Summary: | [68cat][project][sqlite3] Generating a database for SQLite3 and specifying use JDBC for access generates invalid database.yml file | ||
|---|---|---|---|
| Product: | ruby | Reporter: | esmithbss <esmithbss> |
| Component: | Rails | Assignee: | issues@ruby <issues> |
| Status: | NEW --- | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | Generated database.yml file for a JDBC accessed SQLite3 database | ||
Thanks for the report, targeting 6.9. |
Created attachment 90863 [details] Generated database.yml file for a JDBC accessed SQLite3 database [200911091156] [JDK1.6u17] [Built-In JRuby 1.3.1] [jdbc-sqlite3 gem installed] When I create a new Rails project for use with the sqlite3 database and using the jdbc adapter for sqlite3 (jdbc-sqlite3), the application's database yml file is generated without the concept of using jdbc. The user needs to go back in and change the adapter to use the jdbcsqlite3 driver. (See generated database.yml file attached)