Gheorghe Avram
03/25/2019, 9:28 PMGheorghe Avram
03/25/2019, 9:29 PMGheorghe Avram
03/25/2019, 9:30 PMGheorghe Avram
03/25/2019, 9:31 PMRafael Fontoura
03/25/2019, 11:58 PMRafael Fontoura
03/26/2019, 12:05 AM2019-03-25T23:53:45.323196Z 0 [Note] mysqld: ready for connections.
Version: '5.7.25' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)`
- from Prisma GraphQL:
Successfully started 1 workers.
Server running on :4466
Version is up to date.
Rafael Fontoura
03/26/2019, 12:12 AMprisma deploy
the error message Could not connect to server at <http://prisma:4466>. Please check if your server is running
is returned.
I tried to change prisma
to localhost
and the message is the same.Rafael Fontoura
03/26/2019, 12:13 AMhost.docker.internal
then the error message is
Creating stage default for service default... !
! 'ENOTFOUND': request to <http://host.docker.internal:4466/management>
! failed, reason: getaddrinfo ENOTFOUND host.docker.internal
! host.docker.internal:4466
H
03/26/2019, 12:40 AMJames
03/26/2019, 1:51 AMthrow new Error("message")
or are there any special error codes or error objects I should be using?Andrei Bacescu
03/26/2019, 7:19 AMezeikel
03/26/2019, 11:29 AMorderBy
to work with 'createdAt_ASC'
or 'createdAt_DESC'
. Am i missing something? I can query createdAt
in the front end and display it in the UI but can't seem to sort data by itezeikel
03/26/2019, 11:31 AMfeed: async (_, { id }, ctx, info) => {
const following = await ctx.prisma.user({ id }, info).following();
const followingIds = following.map(follower => follower.id);
return ctx.prisma.posts(
{
where: {
author: { id_in: [...followingIds, ctx.request.userId] }
},
orderBy: "createdAt_ASC",
},
info
);
},
impowski
03/26/2019, 12:22 PMprisma@beta
when I mark my custom field with @createdAt
tag it doesn’t generate prisma-client
like it’s supposed toimpowski
03/26/2019, 12:23 PMDateTimeInput
instead of DateTimeOutput
impowski
03/26/2019, 1:30 PMH
03/26/2019, 4:58 PMKristoffer Larsen
03/26/2019, 6:28 PMVinicius Ataide
03/26/2019, 8:17 PMprisma_1 | Exception in thread "main" org.postgresql.util.PSQLException: ERROR: Unsupported startup parameter: search_path
prisma_1 | at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:473)
prisma_1 | at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:205)
prisma_1 | at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
prisma_1 | at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195)
prisma_1 | at org.postgresql.Driver.makeConnection(Driver.java:452)
prisma_1 | at org.postgresql.Driver.connect(Driver.java:254)
prisma_1 | at slick.jdbc.DriverDataSource.getConnection(DriverDataSource.scala:101)
prisma_1 | at slick.jdbc.DataSourceJdbcDataSource.createConnection(JdbcDataSource.scala:68)
prisma_1 | at slick.jdbc.JdbcBackend$BaseSession.<init>(JdbcBackend.scala:453)
prisma_1 | at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:46)
prisma_1 | at slick.jdbc.JdbcBackend$DatabaseDef.createSession(JdbcBackend.scala:37)
prisma_1 | at slick.basic.BasicBackend$DatabaseDef.acquireSession(BasicBackend.scala:249)
prisma_1 | at slick.basic.BasicBackend$DatabaseDef.acquireSession$(BasicBackend.scala:248)
prisma_1 | at slick.jdbc.JdbcBackend$DatabaseDef.acquireSession(JdbcBackend.scala:37)
prisma_1 | at slick.basic.BasicBackend$DatabaseDef$$anon$2.run(BasicBackend.scala:274)
prisma_1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
prisma_1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
prisma_1 | at java.lang.Thread.run(Thread.java:748)
Vinicius Ataide
03/26/2019, 8:20 PMCorey Lanier
03/26/2019, 10:48 PMCorey Lanier
03/26/2019, 10:51 PMIan
03/27/2019, 1:13 AMPRISMA_CONFIG
as a kubernetes secret. I am aware it has some piping formating, does anyone have an example of how that is stored?Dinesh
03/27/2019, 10:12 AMDinesh
03/27/2019, 10:12 AMDinesh
03/27/2019, 10:13 AMDinesh
03/27/2019, 10:13 AMBurim Ameti
03/27/2019, 10:41 AMWill
03/27/2019, 11:36 AMPatrick Nasralla
03/27/2019, 12:23 PM