B4J Tutorial PocketBase - Going behind the scenes with the "--dev" arguement

Hi Fam

In pocketbase there is an arguement that you can pass to your command to start PocketBase that goes behind the scenes and displays each and every command that pocketbase executes internally when your web server application is running. This as a result helped me understand what I needed to do differently in my deployment.

Compatibility: v22.35 (I am not using the latest version of PocketBase)

Some interesting findings...

These do a SELECT * unless you override:

• getList(), getFullList() (REST/SDK) → ✔ full record payloads.

• DAO find helpers (FindRecordById, FindFirstRecordByData, FindFirstRecordByFilter, FindRecordsByFilter, FindRecordsByIds, FindRecordsByExpr) → ✔ full columns.
• RecordQuery(...).All/One with no .Select(...) → ✔ full columns.

When specified, the *fields* option is used to hide other columns and show only the ones you specify (after a select is done)

Proposed Solution(s)

Whilst still limited in functionality e.g. we dont have expand as yet. One will be able to execute own SQL command which will return the *fields* they specify and not use SELECT *.
The route can be called with REST using fetch / httputils etc.

This is available and can be used.

PocketBase - RawSelect (A route/handler to execute SELECT SQL Commands)

Hi Fam Compatibility: v22.35 and below In b4j we have a way of adding routes and writing handler code, same with PocketBase. In PocketBase, one is able to create handlers via javascript and then publish these in the pb_hooks directory and then restart the app to make them live. So, to execute...

www.b4x.com

 

[Mashiane]

Example...

getFirstListItem

INFO GET /api/collections/bma_personnel/records?page=1&perPage=1&filter=emailaddress='???'&skipTotal=1&fields=idnumber
[1.00ms] SELECT `bma_personnel`.* FROM `bma_personnel` WHERE [[bma_personnel.emailaddress]] = '???' LIMIT 1