primary | Simple gem that will help with primary/default records | Messaging library

I have the wackiest bug. Like....the wackiest! If any of ya'll want to put eyes on this, awesomesauce! I really appriciate it! I am creating a survey with REACT, Redux, SQL, HML, Material-ui, and CSS.

I've created a graph of information with am4charts using data from a database. Everything is working and will show up on the page......but not on page load. What I am seeing in my console is that the page will load, it fires off my get request but doesn't return with the data fast enough (I think). By the time that the get request loads, my graph has populated with no data.

Here is the code that I have for the page that I am rendering. What is really odd is that, once my code has run, I can cut a line of code (I've been using a console log). And then the graph will render and load.

I want to Edit data, so for that, I should display it in a form. In my table in the database, I have a primary key named id_casting

So I have he following code :

My script :

I have a simple code where I try to define a vector as one of two initializer lists using a ternary operator:

I have two select form with submit button, I need to get the result of selected value for example

first select form having colours as an option and second contains another things.

and i have some items as div....red flower , red fish.

if i select red from first form its shows red value div and in second form if i select flower it should display red flower only but it's shows everything under the value red. And these all thing must work only when i submit the search button. I have attached jsfiddle below. Code:

Given MySQL tables something like this¹:

First migration file:

I read this answer, which clarified a lot of things, but I'm still confused about how I should go about designing my primary key.

First off I want to clarify the idea of WCUs. I get that WCU is the write capacity of max 1kb per second. Does it mean that if writing a piece of data takes 0.25 seconds, I would need 4 of those to be billed 1 WCU? Or each time I write something it consumes 1 WCU, but I could also write X times within 1 second and still be billed 1 WCU?

Usage

I want to create a table that stores the form data for a set of gyms (95% will be waivers, the rest will be incidents reports). Most of the time, each forms will be accessed directly via its unique ID. I also want to query the forms by date, form, userId, etc..

We can assume an average of 50k forms per gym

Options

• First option is straight forward: having the formId be the partition key. What I don't like about this option is that scan operations will always filter out 90% of the data (i.e. the forms from other gyms), which isn't good for RCUs.

• Second option is that I would make the gymId the partition key, and add a sort key for the date, formId, userId. To implement this option I would need to know more about the implications of having 50k records on one partition key.

• Third option is to have one table per gyms and have the formId as partition key. This seems to be like the best option for now, but I don't really like the idea of having a a large number of tables doing the same thing in my account.

Is there another option? Which one of the three is better?

Edit: I'm assuming another option would be SimpleDB?

I have a given, unmodifiable table design which resembles:

I am trying to make a page responsive but, I am not able to make an image responsive as it is getting off the grid container in material UI. Is there a way I can make the image responsive? I am trying to add the image in Grid container, Still, it is showing the same.