LazyPaginatedMessage explanation
So, I have 500k users in database and I use prisma.
I want to make economy leaderboard with LazyPaginatedMessage but can’t understand how it works and there are no examples for it
I wanted to kinda have method with currentPage parameter, and that will be used to fetch data everytime on page change, right? So I can use “skip” in prisma query
Solution:Jump to solution
As opposed to regular Paginated message it will only execute the page render of the previous, current, and next page. The result is also cached.
40 Replies
Doing prisma.user.findMany and passing that is just crazy and takes too long to load
Solution
As opposed to regular Paginated message it will only execute the page render of the previous, current, and next page. The result is also cached.
.
Pagination (Reference) | Prisma Documentation
Prisma Client supports both offset pagination and cursor-based pagination. Learn more about the pros and cons of different pagination approaches and how to implement them.
LazyPaginatedMessage gives you the page you're on when building the page data so you use that to calculate what to provide to skip and take. Obviously you need to do the calculation yourself since we dont know what of how many and styled how you want to render
it's called @sapphire/paginated-message not @sapphire/paginated-message-for-a-prisma-database-table-that-has-a-very-specific-structure
Is there ANY usage of LazyPaginatedMessage
I just said what the usage is yes
.
Umm there is only discord.js-utilities
Not that
And also there is only example of PaginatedMessage
fine fine
same difference
Not LazyPaginatedMessage
How can lazy and normal one be same
they're not
Which page builder method I use if I want to do this
this says exactly what the difference is
any
So where do I have access to current page
😭 💀
I mean sorry for misunderstanding I just went through whole code of both paginated message classes and can’t understand
Can’t find where LazyPaginatedMessage gives me current page
And where it fetches data only on action
look don't get me wrong but in situations like this the best place to start is to look at the source code of the class. You're asking about fundamentals and that's the only way to get the fundamentals. Furthermore, it's also a way way better method of learning than getting everything served to you on a silver platter.
As I said I already did and can’t figure it out… I’m just looking for a TINY example because there are none to see
I can maybe do like
const menu = new LazyPaginatedMenu()
And that should have index property
And in page builder I call prisma with pagination query
Maybe that?
https://github.com/sapphiredev/utilities/blob/main/packages/discord.js-utilities/src/lib/PaginatedMessages/LazyPaginatedMessage.ts#L25-L48
specifically lines 30-35 and the
addPage calls being function callbacks as opposed to direct executions. Welcome to the JavaScript event loop I guess :floof_shrug: https://www.youtube.com/watch?v=8aGhZQkoFbQ&t=878s&pp=ygUKZXZlbnQgbG9vcA%3D%3DJSConf
YouTube
What the heck is the event loop anyway? | Philip Roberts | JSConf EU
JavaScript programmers like to use words like, “event-loop”, “non-blocking”, “callback”, “asynchronous”, “single-threaded” and “concurrency”.
We say things like “don’t block the event loop”, “make sure your code runs at 60 frames-per-second”, “well of course, it won’t work, that function is an asynchronous ...
g2g now
work meeting
as for this, it's the same as for regular paginated messages
You iterate over the pages in a for loop and add the content for each page. You add this normally, nothing special needed at all. internally we ensure that only that section of code is executed that needs to be executed, as per the code above. I apologise in that I said you receive the page number, that was incorrect of me.
Yeah and that’s why I totally misunderstood everything
I’m probably gonna extend PaginatedMessage and make DynamicPaginatedMessage
Because that’s what I need
How about you start by actually trying LazyPaginatedMessage haha
at least from what I've understood so far you haven't actually tried it yet
No, but I still think that 50k pages in one property is too much
50... K!?
50 000 pages!?!?
bruh
500k members
50k pages
Without extension PaginatedMessage has a limit of 25 because of the select menu but even then you really shouldn't write code that shows that many pages. That's dogshit UX. No one is going to browse past page 1 or 2 at that point.
Mate have you ever used this weird site called https://google.com, how often have you gone beyond page 1
you're asking 50 THOUSAND times that amount
I'm sorry but you're really not using the right tool for the job here. You need to completely rethink your implementation. In fact I'd argue a Discord bot in general isn't even the proper thing to use for this.
Well I want to make economy leaderboard, and there are 500k eligable users in db
Maybe you’re right
What about 25 pages
2.5k users
still seems like a LOT of data and something that could better be shown on a web dashboard but I guess that works. Information density is something to consider as well
@Boomeravna can I disable process.emitWarning
because it's emitted even when I'm only on 25
it shouldnt...
:/
oh wait
thats 250 pages? XD
oh you're right oops haha https://github.com/sapphiredev/utilities/blob/12872de7e65f09dcd3a9071757cf51340a7a336f/packages/discord.js-utilities/src/lib/PaginatedMessages/PaginatedMessage.ts#L751
uh that really should be
> not ===one sec
nono
i was doing 250 pages
not 25
well then you have to extend the class and override the
addPage function to remove that codenono i wanted 25
its ok now
but
if (this.pages.length === 25) { this should be > 25I think it's fine the way it is actually
but uh
oh yea it is
because it first checks and then adds to pages
idk anyways it works thanks