During this meeting, the State Changers extensively discussed various issues they encountered in relation to a task involving database management, particularly record editing and image uploading using Xano.
Key topics touched on in the meeting include: 1. They first grappled with the question of accessing and adjusting records, particularly in relation to indices and user id references within varying user tables. This evolved into a broader discussion about balancing efficiency and readability in SQL, and the pros and cons of sequential queries. 2. The State Changers transitioned to discussing how to tackle the task of uploading images and managing image metadata. They deliberated on how to handle imagemultipart encoding upload and how to use Xano function to extract the image metadata by analyzing the file. A significant amount of the meeting revolved around the challenges and best practices of managing storage within Xano. 3. Insights arose in relation to concerns about continuous state image changes which could significantly impact storage usage within Xano. They considered alternative methods of handling image data like storing as Base64 in the database or using an external service focused on file management. 4. They concluded that if file management is critical for the app, it is probably better to use a specialized service for it rather than trying to manage everything within Xano. As per the discussion, the State Changers found no mention of "WeWeb", "FlutterFlow", "Zapier", "Make", "Integromat", "Outseta", "Retool", "Bubble", "Adalo", "AppGyver", "AppSheet", "Comnoco", "Fastgen", "Firebase", "Google", "OAuth", "Stripe", "Twilio", "Airtable", "DraftBit", "Javascript", "Typescript", "React", "Vue.js", "JSX", "HTML", "CSS", "lambda", "serverless", "State Change", "ScriptTag", "OpenAI", "AI21" in this meeting transcript.
(Source: Office Hours 9/8 )
