In this meeting, the State Changers discussed restructuring a database for the purpose of internationalization, localization, and improved data management practices using Xano. Some of the participants were struggling with the concept of multiple IDs for the same test, which caused confusion when applying the relational model in Xano.
A key point of their discussion was determining the best practices for structuring their local management system (LMS) data and understanding the differences between relational and document models within the realm of database design. They noted the use of SQL, Firebase, MongoDB, and Xano in tackling these models.
Xano utilizes PostgreSQL, which originally functioned as an open-source relational database system but now includes features making it function like a document database. To help structure their data, they considered the utility of adding table references in Xano, but recognized the simplicity of managing relationships through sequences of queries or joins within API endpoints.
In terms of localization, they conversed about implementing a "dictionary" table for translation purposes within their data where all fields that require translation could reference. They discussed the separation of static and dynamic information, deciding the latter should be managed by the back end. This decision led to a strategy where data complexities are managed in the function stack of API endpoints, simplifying both the database structure and the front-end work.
They concluded the meeting by emphasizing the importance of a well-structured back end, admitting that issues often arise for no-coders because they try to jump too quickly into front-end connections before adequately setting up the back end. This effort to make the back end "sing" is not about writing a lot but about delegating the right tasks to the right pieces. Flutterflow and Xano were referenced as tools that help in achieving this.
Keywords: Xano, database structure, internationalization, localization, relational model, document model, SQL, Firebase, MongoDB, PostgreSQL, API endpoints, Flutterflow.
(Source: Office Hours 3/3 )