Chapter 18 making usernames unique

beefycode · August 2, 2018, 12:40am

I’ve been struggling with this for far too long. Not sure exactly what is going wrong here tbh.

when re-writing the Migration extension for adding unique User property I get an error saying that SchemaCreator has no member ‘addIndex’

extension User: Migration { static func prepare(on connection: PostgreSQLConnection) -> Future<Void> { return Database.create(self, on: connection) { builder in try addProperties(to: builder) try builder.addIndex(to: \.username, isUnique: true) } } }

0xtim · August 2, 2018, 1:19pm

It changed slightly a while ago, see:

github.com

raywenderlich/vapor-til/blob/main/Sources/App/Models/User.swift#L65


      
            init(id: UUID? = nil, name: String, username: String, password: String, siwaIdentifier: String? = nil) {
              self.name = name
              self.username = username
              self.password = password
              self.siwaIdentifier = siwaIdentifier
            }
          
          
  final class Public: Content {
              var id: UUID?
              var name: String
              var username: String
          
          
    init(id: UUID?, name: String, username: String) {
                self.id = id
                self.name = name
                self.username = username
              }
            }
          }
          
          
extension User {

beefycode · August 2, 2018, 9:25pm

awesome thanks! hopefully this is changed in the final version fo the book.

beefycode · August 2, 2018, 10:20pm

Incidentally right after this section in the book where you revert your db in Xcode, I did so then launched RESTed to add a new user and password but RESTed was not able to connect to the localhost server. Somehow my postgres db in docker was stopped and not restarted so the app would crash and I got an error that had something to do with NIO not being able to communicate with postgres. I’m no docker expert so I ended up removing the docker image of the postgres and configuring the image again in order to have the db connect again which resolved my issue and I was able to continue.

0xtim · August 3, 2018, 9:12am

@beefycode yep it’s been updated and pending release. Did you laptop restart in that time? If you run docker ps -a you can see all containers, including stopped ones, so you can then just do docker start postgres if it’s stopped

beefycode · August 3, 2018, 6:37pm

@0xtim I may have shutdown my computer overnight, honestly I don’t recall. Either way, I did read up more on docker’s commands and I’m sure re-starting the container like you suggested would probably have been easier, but both methods had the same result and I was able to keep going.

0xtim · August 8, 2018, 12:40pm

Basically the only difference is you’d keep the existing data. Glad it’s working though!