meme | A meme generator , from the fine folks at DailyDrip | Learning library

You can use simply intent.putExtra instead of worrying about which variant like put_____Extra to use.

When extracting the value, you can use intent.extras to get the Bundle and then you can use get() on the Bundle and cast to the appropriate type. This is easier than trying to figure out which intent.get____Extra function to use to extract it, since you will have to cast it anyway.

The below code works whether your data class is Serializeable or Parcelable. You don't need to use arrays, because ArrayLists themselves are Serializeable, but you do need to convert from MutableList to ArrayList.

In Kotlin you have to instantiate properties with backing field in the construction (getting them from constructor, assigning them some value, or fill them in init blocks). And the only exception is lateinit var. In the first code, you're getting them in constructor. But in second one, they're introduced without being initialize so compiler asks you to either fill them, or convert them to non-backing field by providing getter and setters.

But if you want to make the first code Serializable you have to simply make that implement Serializable like this:

You need to load the extension using the name which matches the filename, i.e. bot.load_extension('fun').

As for the "self is not defined" error, that is because you declared your class as a subclass of self, which is not defined. Instead, do the following:

At my job I support MySQL instances that have multi-billion row tables. At that scale, care must be taken to optimize queries properly. You don't want to do a table-scan at that scale.

But that's about rows, not columns. You asked first about columns.

The way to choose between adding a column versus adding another table is to follow rules of database normalization. If the new column is for an attribute of the same entity as your current table, add the column to that table. If it's a multi-valued attribute or if it's really an attribute of some other entity, then add it to a different table.

Very, very rarely is it the right choice to make another table solely for the sake of having too many columns. A given MySQL table can have dozens of columns pretty easily, and hundreds if you're careful.

In theory, there is no limit to the number of columns that might be appropriate to put in the same table with respect to normalization. But there are limitations due to the code to store those columns in a given implementation (e.g. InnoDB storage engine in MySQL).

See https://www.percona.com/blog/2013/04/08/understanding-the-maximum-number-of-columns-in-a-mysql-table/

So the maximum number of columns for a table in MySQL is somewhere between 191 and 2829, depending on a number of factors.

In the comments on that blog, I was able to design a table that failed to be created at 59 columns. Read the blog for details.

Looks to me like schedule and threading are overkill for your use case as your script only performs one single task, so you do not need concurrency and can run the whole thing in the main thread. You primarily just need to catch exceptions from the main function. I would go with something like this:

Change adapter = new Adapter(getApplicationContext(), arrayList); to

Instead of going to every path you can use below code :

The reason is praw and asyncpraw. As they are not made for getting posts, you shouldn't be using them. You can use RedditEasy which is 2x faster than praw in getting posts.

There is no need for you to iterate over anything. Praw provides a method which allows you to grab a random submission from a subreddit.

Documentation: random()

Code: