Speed Up Your Backend with Xano Transform
ฝัง
- เผยแพร่เมื่อ 5 ส.ค. 2024
- The Xano Transform Engine is a powerful new way in Xano to filter and manipulate data, as an extension of our dot notation feature. Using an easily human readable syntax with the Expression data type, you can quickly parse, filter, and transform your data at lightning speed compared to utilizing functions such as For Each loops.
00:00 Intro
01:33 Dataset Overview
02:18 Example 1 - Combining First + Last Name
05:25 Example 2 - Fixing inconsistent phone number data
09:10 Example 3 - List users associated with each company
14:13 Outro
Xano - The Fastest No Code Backend Dev Platform
go.xano.co/3KcR86z
Twitter
/ nocodebackend
Subscribe to Xano's Channel for Weekly New Content
/ nocodebackend - วิทยาศาสตร์และเทคโนโลยี
Insane how performant the transform expression looks.
Thanks for another great video. I am a newbie, but in the past few weeks, I've come to appreciate that the real power of Xano is its Function Stack. So much business logic, filtering, data transformations, and integrations can be added to the backend.
Thank you for this. The ability to combine code with no-code is a real benefit. I literally transformed an array of 400 big objects with map lambda in the way that i would like it to bereturned. It took couple of miliseconds, where looping took 4-5 seconds. Combining lambdas and sql database querry can do massive things in couple of miliseconds.
This is great to see. What would be an amazing feature is to be able to convert an existing function group into the Xano Transform expression. Or even a way to copy the details of a selected list of functions and being able to paste it into the Xano AI to get an expression back.
Yep, gotta learn this! Amazing!
Amazing like always. ❤
Woah! Excellent content Chris and what a great comparison. I've just started using the Xano Transform data type for simple use cases but knowing how performant it is for more complex situations means I'll be using it a lot more in the future.
Would be great it this could be used with a "bulk Update records" instead of a "For Each loop"+"Edit Record".
For the Full name thing - if we use the eval then it will be faster than for each loop?