wastebasket | A crossplatform go library for moving files to the trashbin

I will be glad to help.

You can use something a little like this:

Instead of if get(modmailchannel, name=f"{message.author.name.lower()}{message.author.discriminator}"): use:

Your error is saying exactly what is your problem.

There are two problems there:

1. i will not be the value you expect in the callback because you declared it outside the loop. See this question's answers for why, but basically, you'd put the let inside the for statement in order to make the i your event handlers close over be relevant to the handler. But, there's no need for that, just use this inside the handler instead.

2. You're relying on the number of .js-name elements to be exactly the same as the number of .js-listendelete elements. Maybe that's reliable, but there's a more reliable way.

And optionally:

1. Hooking the handlers directly to the elements is fragile; if you add more elements later, you have to remember to hook them up.

What I'd do instead is use event delegation and then traversing the DOM:

• Event delegation: hook click on the table (or table body) and then see if the event passed through a .js-listendelete element on route to the body as it ubbled.

• Traversing the DOM: If it did, I'd use parentNode or closest() to go up to the row, then get the row's first td.

Here's an idea what that would look like:

The only way to reduce the usage of your storage without temporarily taking more space is to DROP TABLE or TRUNCATE TABLE, and even that will reduce space only if you have the option innodb_file_per_table=ON (this is on by default since MySQL 5.6).

Many types of ALTER TABLE operations make a temporary copy of the table, which creates a new tablespace. Refer to https://dev.mysql.com/doc/refman/5.6/en/innodb-create-index-overview.html and notice every type of ALTER TABLE that is noted with "Rebuilds table: Yes"

Rebuilding the table means creating a new table, copying all the data from the old table to the new table, while adapting to changes in columns in the new table, then swapping the new table for the old table, and finally dropping the old table. This takes time for a large table, and temporarily requires storing both the table and the new table simultaneously.

Basically, any alteration that changes the size of a row, like adding/dropping columns, changing datatypes of columns, or even changing the nullability of columns, rebuilds the table. There's no way to drop a column quickly or without temporarily using more space.

Some other types of ALTER TABLE, like dropping secondary keys, free up database pages in the tablespace, without rebuilding the table. But those pages are still held by the tablespace and recycled by subsequent data or indexes.

A tablespace never shrinks. It can only be dropped, or else defragmented as it's copied to a new tablespace.

So it's up to you to make sure there's at least enough free disk space to store an second copy of your largest table (plus binary logs if they are stored on the same volume, but I don't know if RDS stores binlogs on the same volume).

Nevermind, I finally figured it out. I had to loop through the collection first. Once I do that create another loop inside it to loop over it's structured values.