this.belongsTo is not a function

[brenolf]

I'm trying the basic example shown in the docs but I'm getting the title error. The code I'm running is as follows:

'use strict'

const Lucid = use('Lucid')

class Opinion extends Lucid {
  user () {
    return this.belongsTo('App/Model/User')
  }
}

module.exports = Opinion

And using like:

let opinion = new Opinion
opinion.user().associate(user)

Should I create it before associating?

[thetutlage]

how have you created the user variable ?

[brenolf]

Forgot that! Here it is:

let user

try {
  user = yield User.find(request.param('id'))
} catch (e) {
  response.notFound()
  return
}

let opinion = new Opinion

opinion.liked = request.input('liked')

try {
  opinion.user().associate(user)

  yield opinion.create()

  response.created()
} catch (e) {
  response.internalServerError()
}

[thetutlage]

also can you tell what error you get ?

[brenolf]

I get the title's error: this.belongsTo is not a function on return this.belongsTo('App/Model/User') line

[thetutlage]

This is wierd , let me reproduce it

[thetutlage]

All worked great for me , sharing my code

const user = yield User.find(1)

if(Object.keys(user.attributes).length === 0){
  return 'Not found'
}

const opinion = new Opinion
opinion.user().associate(user)

const created = yield opinion.create()
if(created && created[0]) {
  return 'All Good'
}

return 'Sorry unable to save your opinion'

Couple of things to note here

1. Lucid only throw error when something goes wrong , like some field in the table does not exists and so on. So there is no need to have multiple try/catch blocks as the final request handler will handle these exceptions for you.
2. Right now you have to the use the dirty way to check whether User.find(someId) worked or not by checking the length of attributes on user instance, but as i am working to improve the entire framework later these types of error checking will be easier.

[brenolf]

Weird. I keep having the same error. Any ideas on what could it be?

Thanks for the notes btw.

[thetutlage]

what version of lucid u using ?

[brenolf]

1.0.2

[thetutlage]

Ohhhh , relationships have been introduced in v1.0.3. Solved :)

[brenolf]

Just updated here and now it works! My bad, sorry about that.

[thetutlage]

No issues , docs needs to have upgrade section

[shanthakumarf22]

on ^6.1.3 still having this issue. looks like its related to something else.

[herickwilke]

on ^6.1.3 still having this issue. looks like its related to something else.

I'm having the same issue.

"@adonisjs/lucid": "^6.1.3",

[zelucena]

I've just had this issue with two relationships in which none were named 'foreigntable_primarykey'; both were just 'foreigntable'. I tried creating a new column in my DB with the expected naming system and it worked.
Eg: this.belongsTo('App/Models/Client', 'client', 'id') -> won't work
this.belongsTo('App/Models/Client', 'client_id', 'id') -> works properly

Update:
Actual error message I wrap with try..catch:
"select * from client where client.id in ((select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client)) - ER_OPERAND_COLUMNS: Operand should contain 1 column(s)"

The is a big problem for me, as I am working with legacy code alongside sharing this database and I should not modify the current database structure.

[Benez11]

@thetutlage

I've just had this issue with two relationships in which none were named 'foreigntable_primarykey'; both were just 'foreigntable'. I tried creating a new column in my DB with the expected naming system and it worked. Eg: this.belongsTo('App/Models/Client', 'client', 'id') -> won't work this.belongsTo('App/Models/Client', 'client_id', 'id') -> works properly

Update: Actual error message I wrap with try..catch: "select * from client where client.id in ((select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client), (select * from client)) - ER_OPERAND_COLUMNS: Operand should contain 1 column(s)"

The is a big problem for me, as I am working with legacy code alongside sharing this database and I should not modify the current database structure.

@thetutlage I'm in a similar condition. Any resolution for this?