As part of my job, I order a variety of clothes for a variety of people.
Currently, I have a table (table one) that lists each item to be purchased, the type of item, who it's being purchased for, and how many of each size (examples of each below).
In addition to all fruit purchase information in the Main Table, I would like to create three new tables: Apples, Oranges, and Bananas that only contain the purchase history of the one respective fruit. I don’t know of any way to implement precisely what you’ve described – but there may be ways to provide you with equivalent functionality.
Is there a way to update all the three columns in one shot or another way that update can be done?
update Table A set Col X = ( select Col X from Table B where Col W = Table A.
The first is USERS with id, name, unredeemed_points The second is POINT_ALLOCATIONS with id, user_id, activity, point_value.
I need an update script that will update USERS.unredeemed_points with the total (SUM) of all the POINT_ALLOCATIONS.point_value for each My current script fails when it does not find any matching records in POINT_ALLOCATIONS because USERS.unredeemed_points is flagged as Not Null.
Again, while none is an exact match for your needs, in each case the desired behavior required moving information through Airtable in a manner not explicitly supported by an internal function. I'm in the final of configuring a performance (musician's) BD.
Very excited about all the news possibilities :slight_smile: This is my problem: I am assigning concerts to groups made of 2 or 3 musicians.
Col W ); Your database management system should be able to see that for each row in Table A, all three correlated sub-queries access the same row in Table B.
Therefore, it should optimize the query so that it is only accessing the row in Table B once for each row in Table A.
Every time I sell a fruit, I record it in the Main Table by selecting the fruit in a dropdown menu with other purchase information like customer name, date and time of purchase, etc.
The dropdown menu is multi-select since customers can buy more than one kind of fruit at a time.
Existing values will not be set to 0 when there are no more related records in point_allocations.