Hi I’m trying to develop a booking system but I couldn’t find a way to make my records unique. I mean if there is reservation for a specific date and a specific room, no other reservations would be accepted. I couldn’t find a way from Docs or from past Community posts. Can anyone help ?

[image] mortar_board Advanced Booking App Tutorial (Step-By-Step) Community Resources [🎓 Glide Tutorial - Advanced Booking App (Full Course & Cheat Sheet)] What’s up Gliders! Thought I’d share my latest free tutorial for those that might be interested. popcorn …

Hi, Darren_Murphy! Have you also think it is possible to prevent overbooking with client side calculation(as for now in Glide)? I have read this manual several times and i don’t understand how it possible. Off course possibility of overbooking is very small, but in atcually it possible(overbookin…

Yes, you’re right. Because the operations are not atomic, there is always a small chance that collisions can happen and you wind up with duplicates. A while back, David suggested using something like Upstash with Redis to handle this. I’ve not had a need to try it yet, but I’ve been keeping it in t…

Yes, i already use Upstash Redis solution instead Make, because with make it will require 2 paid update, but with Redis is only one. I’m just curious that fact of above tutorial many times suggested as solution, it is excellent for study, but not for production. Thanks to confirm, because in a befo…

[image] slscustom.ru: May be it is not right topic for this question, but: Does add row action is atomic? Does it firstly add row to server, then receiving answer and then ready to run “On submit action”? I believe that rows are added locally, and then subsequently synced with the Glide bac…

So, it mean we exactly need external service just simple, for unique Order’s serial number. Native row id is unique, but not a serial and not human’s friendly readable. Thanks again!

But in which order they have been added to server? As they actually arrived to server or as they actually created(user’s side quantized to global Unix milliseconds?)

Why does that matter? Rows are rows, ordering is unimportant. If your App functionality depends on the ordering of rows in the underlying tables, then you are doing something wrong (and violating the first rule of database normalisation).

For now I’m sending Row ID to Redis and they respond me serial number which i saving in Glide table in the row which Row ID has send to Redis, but it requires one paid update. For all computation i using Row ID, Serial just for showing to users and during user’s searching from app interface. p.s. …

Uniqueness of rows

Ask for Help

Darren_Murphy February 6, 2024, 8:13am 2

Topic		Replies	Views
Unique Counter to avoid duplicates Ask for Help	12	353	December 19, 2025
API call not able to read it Ask for Help	11	310	March 20, 2024
Serial number in glide tables Ask for Help	9	1561	December 20, 2021
🗓️ Simple Booking App Tutorial (No Double Bookings) Community Resources tutorial	35	3001	September 13, 2025
Built in locking or semaphore mechanism Feature Requests	51	1144	July 5, 2021

Uniqueness of rows

Related topics