specifications

I have the following database model: A aId AB aId bId B bId status In a Spring data Specification, I want to return the instances of A when B.status is 'X'. The JPQL code is the following: select a from A a where a in (select ab.id.a from AB ab where ab.id.b.status= :status) These are the model classes: @Entity public class A { private Long aId; @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL, mappedBy = "id.a") private Set<AB> ab; } @Entity public class B { private Long bId; private String Status; @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL, mappedBy = "id.b")

I frequently find myself wanting to make a table of forms -- a bunch of rows, each row being a separate form with its own fields and submit button. For instance, here's an example pet shop application -- imagine this is a checkout screen which gives you the option to update the quantities and attributes of the pets you've selected and save your changes before checking out: Pet Quantity Color Variety Update snake 4 black rattle update puppy 3 pink dalmatian update I would love to be able to do this using HTML that looks like this: <table> <thead><tr><th>Pet</th> <th>Quantity</th> <th>Color</th>

This GridLayout is going in my app that has a lot of levels. Each level has a different number of rows and columns. I assume that this GridLayout would be my best bet to use to satisfy my needs. Also, all need to be done at runtime prorammatically. I am having trouble understanding how to use GridLayout.spec() . I am trying to follow this excellent example but just cannot grasp it fully. Let's say, for example, I want a GridLayout with 3 columns and 4 rows. GridLayout.LayoutParms params1 = new GridLayout.Layout(rowSpec, columnSpec); //what's parameters? gameplayGridLayout.setColumnCount(3);

I was experimenting with how / is interpreted when around different keywords and operators, and found that the following syntax is perfectly legal: // awaiting something that isn't a Promise is fine, it's just strange to do: const foo = await /barbaz/ myFn() Error: Uncaught ReferenceError: await is not defined It looks like it tries to parse the await as a variable name ..? I was expecting await is only valid in async function or maybe something like Unexpected token await To my horror, you can even assign things to it: const await = 'Wait, this actually works?'; console.log(await); Shouldn't