

Or how about during development when you just want to create a SQL statement using a number of variables. Properties should be available before/after you interact with the database? You might fill most of the properties after loading the data from the database and thus the object is less useful before being loaded. Isn't it frustruating managing the lifecycle of those objects? For instance you may initialize an instance of the object and fill some of its properties prior to doingĪ look up to a database. Good question! Have you ever built a large library of classes that supports your business logic and thus you have properties mapped to your database model? What is the "SQLdeLite.Record" class represented above as the SQLdeLiteRecordObject? CreateInsertStatement(databaseObject, TableNameAsText, TableAndFieldNamesQuotedAsBoolean).SQLdeLiteExecute(sqlStatementAsText, SQLdeLiteRecordObject).

SQLdeLiteSelect(sqlStatementAsText, SQLdeLiteRecordObject).SQLdeLite is built on top of the new Xojo framework and ready for the future.SQLdeLite is HALF the size contained inside a single module.SQLdeLite can use classes or dynamic objects via SQLdeLite.Record.
#XOJO DATABASE EXAMPLE CODE#
#XOJO DATABASE EXAMPLE FULL#
Full support for all Xojo supported databases.Full support for iOSSQLiteDatabase on iOS! You can use the same business logic between projects despite using different database backends.Built on top of the new Xojo framework.Now it's much faster to handle your query parameters and results. Dynamic objects that allow for any number of properties without having to define each one in the IDE.No more string concatenation for your SQL!.These variables are converted to the bounded parameters in prepared statements. Quickly and easily create SQL queries by using variables representing the properties of your objects.Automatically uses SQL prepared statements mitigating SQL injection attacks and speeding up database performance.Single drop in module that speeds up your development.
#XOJO DATABASE EXAMPLE PC#
I do direct connections from my own machine to databases in ‘the cloud’ but I would definitely be hesitant about allowing another PC to do that.SQLdeLite is an open source library that allows you to speed up your database development with Xojo. In the end I guess it depends on how important the security of the data on the website database is to you, and how much control you have over the remote machines. Depending on how complex the operations you are trying to perform are, it could be fairly simple to write your own web application in xojo to sit between the remote machines and the db. It should include authentication and encryption. Even if you know the IP addresses of the remote PCs that are connecting and can limit access very carefully, if any of those machines gets a virus, etc you could still be vulnerable.įrom a security standpoint, a safer approach (although more work) is to create a middleware layer, like a REST API service for instance, to handle data coming in and out from your remote machines. Exposing the website database to direction connections over the internet creates some security issues.
