chore: create permit table and move data

[seprintour]

Resolves #811

Quality Assurance:

More QA: Seprintour-Test/test#41 (comment)

I also changed the datatype from char to varchar to fix this error Seprintour-Test/test#41 (comment) @pavlovcik

[netlify]

✅ Deploy Preview for ubiquibot-staging ready!

Name	Link
🔨 Latest commit	3d46590
🔍 Latest deploy log	https://app.netlify.com/sites/ubiquibot-staging/deploys/6523e49b5607da0008773cf4
😎 Deploy Preview	https://deploy-preview-817--ubiquibot-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[seprintour]

@pavlovcik PR attached

[0x4007]

The bot is expected to be stable after these changes are implemented which implies that all of the functions that interact with the database should also be refactored to accomodate this new architecture.

From #787

Shouldn't you refactor functions that interact with these tables?

[seprintour]

From #787

Shouldn't you refactor functions that interact with these tables?

Yea, I would do that now..

[seprintour]

Shouldn't you refactor functions that interact with these tables?

check it out now, i ran into some more issues and fixed.. check description

[0x4007]

Code looks good just have some rename requests

[seprintour]

Code looks good just have some rename requests

Fixed issues

[seprintour]

Ping @pavlovcik @whilefoo

[whilefoo]

I'd rather not use char(x) because we've had some problems in the past related to that because either Supabase or PostgREST library wasn't working correctly, so I would just use TEXT with CHECK (char_length(name) <= x)

Even if we ignore the bug with char(x), people are mostly recommending to use text because char and varchar have some limits

[seprintour]

Even if we ignore the bug with char(x), people are mostly recommending to use text because char and varchar have some limits

@pavlovcik what's your thought on this, and did the schema change again?

I'm seeing some changes on the parent issue

[0x4007]

To be honest I spent a significant amount of time trying to completely redo the database and functions that interact with it. I seem to have underestimated the amount of work involved but it forces me to become intimately familiar with all of these technologies and concepts within our bot.

It might be more productive to focus efforts elsewhere this week as I continue my research

[0xcodercrane]

The EVM address we're currently using has a fixed size 42. so no need to set varchar(42) type for them

[seprintour]

@0xcodercrane @whilefoo i made it a text with a length constraint like agreed

[whilefoo]

@seprintour can you make new QA issue to make sure everything is working?

[seprintour]

@seprintour can you make new QA issue to make sure everything is working?

Sure