database adapters not working
- Langage dominant
- JavaScript
- Étoiles
- 1.6k
- Forks
- 179
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hey i just started to play around with compound and its ORM, but... the database choices seem to be failing for me. I prefer the coffeescript, _but tried with plain JS, too._
The workflow is basically the same across all my attempts, and i am using osx 10.9 mavericks:
`compound init noir-eso --coffee -css less --db [one of below]`
`cd noir-eso`
`npm install`
`compound g crud race name image text markdown`
`compound db create`
`compound db migrate`
`compound s`
--> go to /races and try adding a new record
**sqlite3**: automigrate/autocreate just doesn't work. Changed database settings to a concrete file, and my inspection tool shows that there is no table created.
**mysql**: the "mysql is not installed" error seen in another ticket here. none of the solutions help.
**nano**:
```
[...]/noir-eso/node_modules/jugglingdb-nano/lib/nano.js:23
return db.insert(design, '_design/nano', function(err, doc) {
^
TypeError: Object # has no method 'insert'
```
**firebird**: `[Error: ENOENT, no such file or directory '/usr/local/lib/node_modules/compound/templates/config/database_firebird.coffee']`
redis isn't suitable for my planned project, mongoDB seems to work, but isn't really suitable, too.
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
The issue reports failures with multiple database adapters (sqlite3, mysql, nano, firebird) in the Compound ORM. Start by checking the database configuration templates in /usr/local/lib/node_modules/compound/templates/config/ and the adapter implementations in node_modules/jugglingdb-* directories. Look for missing methods like 'insert' in nano.js and test the automigrate flow. The goal is to identify why table creation fails and adapters throw errors.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- coffeescript, javascript, mongodb, mysql, redis, sqlite
- Domaine
- backend, databases
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 30/100