
PostgreSQL support for Blueprint projects that need SQL reads, writes, image storage, and clean result parsing.
PostgreSQL lets Blueprint users connect with host, database, login, password, and port fields, then run queries and receive results through Blueprint events. It is a good fit when your project already uses PostgreSQL or needs image data stored in the database.
Fill in server, database, login, password, and port fields directly in Blueprint.
Use advanced fields for SSL, timeouts, and project-specific connection needs when required.
Update UI, loading states, and retry flows when connection, select, or update actions finish.
Read rows, columns, and values in Blueprint so results can be shown in UMG or saved into game data.
Run leaderboard, account, inventory, analytics, or admin-style select/update queries from Blueprint.
Store and read image data through the PostgreSQL Blueprint flow when your project needs database-backed images.
Use the same Blueprint-style flow to connect, check status, run queries, and close the connection.
Run select, insert, update, and delete SQL from gameplay or editor tools without freezing the project.
Read query output as Blueprint-friendly rows and columns for UI tables, save data, and admin screens.
Place the actor or add the component, fill in connection fields, bind events, connect, and run queries from Blueprint.
Show loading, success, failure, and retry states in your UI with Blueprint events.
Use optional fields for SSL, timeouts, custom ports, or full connection strings when your project needs them.