Alexander
05/21/2019, 1:52 AMprisma deploy -e .env
, this process fail and i go to the logs in container, it show me this Encountered unknown SQL type timestamptz with column last login. IntrospectedColumn(last login,timestamptz,null,true)
. How can i fix this ? I am using postgres. Thanks for you helpHyo
05/21/2019, 2:40 AMprisma
with our production service. Is this ok to use prisma
v1 when prisma2
is comming? I am afraid if there could be any heavy migration issue.gem
05/21/2019, 11:16 AMHoang
05/21/2019, 1:02 PMHoang
05/21/2019, 1:02 PMException in thread "main" java.lang.RuntimeException: Unable to load Prisma config: com.prisma.config.InvalidConfiguration: Expected user to be non-empty
at scala.sys.package$.error(package.scala:26)
at com.prisma.config.ConfigLoader$.load(ConfigLoader.scala:40)
at com.prisma.local.PrismaLocalDependencies.<init>(PrismaLocalDependencies.scala:48)
at com.prisma.local.PrismaLocalMain$.delayedEndpoint$com$prisma$local$PrismaLocalMain$1(PrismaLocalMain.scala:13)
at com.prisma.local.PrismaLocalMain$delayedInit$body.apply(PrismaLocalMain.scala:8)
at scala.Function0.apply$mcV$sp(Function0.scala:34)
at scala.Function0.apply$mcV$sp$(Function0.scala:34)
at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
at scala.App.$anonfun$main$1$adapted(App.scala:76)
at scala.collection.immutable.List.foreach(List.scala:388)
at scala.App.main(App.scala:76)
at scala.App.main$(App.scala:74)
at com.prisma.local.PrismaLocalMain$.main(PrismaLocalMain.scala:8)
at com.prisma.local.PrismaLocalMain.main(PrismaLocalMain.scala)
Hoang
05/21/2019, 1:16 PMHoang
05/21/2019, 1:17 PMprisma deploy
Hoang
05/21/2019, 1:17 PMHoang
05/21/2019, 1:18 PMprisma --version
Prisma CLI version: prisma/1.33.0 (darwin-x64) node-v8.15.1
Prisma server version: 1.33.0
Francis John
05/21/2019, 8:05 PMJscott388
05/22/2019, 1:58 AMJeff
05/22/2019, 2:07 AMFloat
type allows? I'm trying to mutation something like -79.39048179999998, but it keeps showing up as "0.000000000000000000000000000000"Jidé
05/22/2019, 7:06 AMJidé
05/22/2019, 7:06 AMlabels: [String] @scalarList(strategy: RELATION)
Jidé
05/22/2019, 7:07 AMOliver Evans
05/22/2019, 7:36 AMmy-service
and a stage dev
deployed. I can access it within my cluster via graphql playground without an issue at <https://internal-service-address/my-service/dev>
. Now, I want to make it externally available at <https://my-website.com/prisma-dev>
, so I have nginx routing <https://my-website.com/prisma-dev> -> <https://internal-service-address-my-service/dev>
.
If I send a graphql query to <https://my-website.com/prisma-dev>
, then I get
{
"errors": [
{
"message": "Project not found: 'prisma-dev_default'",
"code": 3016,
"requestId": "local:cjvywtsd8z7160999t2tfncc0"
}
]
}
and if I send a query to <https://my-website.com/prisma-dev/my-service/dev>
, then I get
{
"errors": [
{
"message": "Project not found: 'prisma-dev~my-service_dev'",
"code": 3016,
"requestId": "local:cjvywxpufz71d0999cn56um0b"
}
]
}
Is there a recommended way to deal with this situation?
Thanks!
OliverHoang
05/22/2019, 12:00 PMtimestamps: true
?Matthew Sheets
05/22/2019, 2:46 PMMatthew Sheets
05/22/2019, 2:46 PMJared
05/22/2019, 4:57 PMbresson
05/22/2019, 9:57 PMlewisedc
05/23/2019, 10:18 AMstephan
05/23/2019, 11:40 AMSachin Jani
05/23/2019, 12:54 PMMatthew Sheets
05/23/2019, 5:04 PMgem
05/23/2019, 7:14 PMahebwa49
05/23/2019, 8:05 PMMike
05/24/2019, 3:28 AMGambo
05/24/2019, 4:51 AMMatteo
05/24/2019, 12:07 PM