Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Theo
@shierro
ah yes, i was looking for the raw option, and yes for CURRENT_TIMESTAMP thanks @wzrdtales you're awesome
this is useful. although i haven't been able to see it in the docs. might be good if we can add it there for future reference
Tobias Gurtzick
@wzrdtales
np, it is not yet in the docs, and not yet in all drivers
I intend to add a special property as well
where I can put well known functions like current_timestamp across the board
and keep raw for the unique stuff
brirtch
@brirtch
Hi. I'm getting an error [ERROR] Error: Environment(s) 'all' not found. My database.json file just contains one line: {
"all": {"ENV":"DATABASE_URL"}
}. Can you assist?
This is only happening within a Heroku release, not locally
brirtch
@brirtch
and using command: db-migrate up --config config/database.json -e all
Tobias Gurtzick
@wzrdtales
you're using that wrong
first of all never name your target config all
all is a reserved key in a lot of cases
second of all, when you want to use DATABASE_URL you do not need any db config at all normally
and the error happens b/c the environment variable is not set
you need to check on your side why
Dmitry Dzhus
@dzhus
Hey all, I can't find anything on the status of COPY support – is it expected to work if I want to manage some custom data in migrations too? currently getting this on 0.11.5:
received data: CREATE TABLE test_data (col1 text, col2 text);

COPY test_data (col1, col2) FROM stdin;
a       b
c       d
\.

[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: syntax error at or near "a"
dimtabu
@taburetkin

guys stupid question about installation
i am confused...
npm install -g db-migrate - done
creating the migration: db-migrate create initial

and the result is like this

'use strict';

var dbm;
var type;
var seed;

/**
  * We receive the dbmigrate dependency from dbmigrate initially.
  * This enables us to not have to rely on NODE_PATH.
  */
exports.setup = function(options, seedLink) {
  dbm = options.dbmigrate;
  type = dbm.dataType;
  seed = seedLink;
};

exports.up = function(db) {
  return null;
};

exports.down = function(db) {
  return null;
};

exports._meta = {
  "version": 1
};

this is definitely not the same as in docs
and i think its from another package at all
or... docs are a little bit wrong?

ethanwllms
@ethanwllms
hello all! I am new to using db-migrate. I am needing some help with a small ..error? I'm getting a reply that require db-migrate-mongodb and ./mongodb are needed I believe. I can supply the full return if needed. This is all coming from the verbose print btw
@taburetkin I believe the docs are at least a few minor releases behind. That is my suspicion anyways.
Eduardo Tamaki
@eduardotamaki
Hi, Is there a way to generate a migration file for the current database?
at1217
@at1217
Hey There, does any of you know how to set a default decimal place for decimal data type inside of the exports.up variable?
I have done like "column_name { type: 'decimal', length: '10,2'}" and "column_name {type:'decimal', precision: 10, scale: 2}"
But none of these works...
Karenina
@Karenina444_twitter
hi guys
can you point me to examples of this framework please?
Josh Ydenberg
@jydenberg

Hi Guys, I am getting an error only when using sync down() in a scoped environment.
I am using the programmable API and a driver i am developing to support another DB System.

Every other command seems to work fine, including syncing up migrations.
When the sync down parses the path from the migrations listed in the DB, it has the

issue that the directory and the name (which includes the subfolder), get appended.
Say my scope is "stores" the directory it is trying to access appends the scope name and becomes "/mypath/stores/stores/migrationName.js" instead of "/mypath/stores/migrationName.js". The scope name is already included in the migration table name, and seems expected int he migrator file.
Did i implement something wrong in my driver? every other operation seems to work, sync using scope up works, and sync down with no scope works - just this edge case is broken.
Josh Ydenberg
@jydenberg

Under the "migration.js" file (db-migrate/lib/migration.js), there is the "loadFromDatabase" function. the dir parameter which is passed in already had the scope appended, but then it is also retreived in the name returned by the db. Then of course it fails with a "module cannot be found" error since the filepath is incorrect.
Is this a generic bug or is my driver implementation wrong?

For example ->
i run sync("20200110", "myscope)
Dir parameter passed in is "a/b/c/migrations/myscope" when i r
Migration is retreived myscope/mymigration
They get appended and it defines the path as "a/b/c/migrations/myscope/myscope/mymigration", which throws an error.

Is there a workaround for this or someway for up/down by date to work with the API?
Thanks!

Josh Ydenberg
@jydenberg
Any ideas about above? Still seeing this issue