#How should I store very long text?

28 messages · Page 1 of 1 (latest)

valid pivot
#

The max string length I can't find but I know it's not very big right, like 10000?

devout oxide
valid pivot
#

I could chunk it up and give each one the same book_id but not the best solution

#

but wasn't sure if it was something that was interesting or

devout oxide
valid pivot
#

how big does it go?

#

I was trying to find the max size for it, google didn't help though I didn' search the appwrite docs that well

devout oxide
valid pivot
#

hey do you guys want an AI bot that can answer questions for you on Discord?

#

I feel like if you indexed your documentation and put it inside something like Danswer you could have it try to answer questions ahead of time and you just approve the answer if it's easy

#

I already have it indexed, I can host it if you'd like

#

right but do I need to go into the DB directly and add this value?

#

As you can see, even TEXT in MariaDB has some limitations regarding length. If you want to be extra safe, I would recommend LONGTEXT by setting size to 16777216. That will under the hood create A LONGTEXTTEXT column with a maximum length of 4,294,967,295 or 4GB ( 2^32 - 1 ) characters..

devout oxide
valid pivot
#

if you link the endpoints to a simple discord bot instead it would probably be the easiest thing to do

#

I can do it if you'd like next week, let me know if you are interested

devout oxide
valid pivot
#

yeah I tried that I'm confused though because before if I had too many attributes with like 6000-12000 it would have given me an error about size

#

that's why I was asking like that

#

maybe it was in the old version I was using

devout oxide
devout oxide
valid pivot
#

I assume that means I need a new database?

#

ohhh I gotta make it bigger