In a recent Star Trek Discovery episode, the crew was investigating how a probe (from the future!) was attempting to hack into their systems. This is what was said about it:
It’s very usual to use encrypted SQLite databases in our Xojo projects where we expect to get the maximum read speed from them. But the truth is that encrypting the data in these databases can introduce a penalty in our queries, both from read and writing/updating data to them. How can we improve this? One technique is the creation of a new in-memory based SQLite database, where we will be able to copy the table (or tables) we are interested in getting the maximum speed possible with. Continue reading to see how to do this.
If you are using SQLite you might be trying to share your database. What are your options when you want to be able to share your database?
Do you need to know what version of MySQL you’re using in code? Maybe you need one of the many other configuration parameters that MySQL offers? It’s easy to get this information with some simple code!
Whether you are new to building database applications or you need to expand your toolbox, Xojo is a smart choice. With Xojo you can build real, native apps. And Xojo’s powerful language allows for rapid app development while supporting a wide variety of databases and ODBC, plus it offers flexible form design, database binding, reporting and more.
Noted recently at the SQLizer blog, the SQL language was first created 43 years ago. And what is remarkable about that is that SQL is still used today. According to the Stack Overflow 2017 developer survey it is the #2 programming language. Not many languages remain in use for such a long period of time. Although we’re happy to also note that Xojo celebrated our 20th anniversary in 2016!
I’ve ran into PostgreSQL case sensitivity myself before and I’ve seen it come up on the forums, so I thought it might be a good thing to bring up here.
Sometimes you hear that PostgreSQL is case-insensitive, but it isn’t really. What it actually does is convert your SQL to lowercase by default. So take a look at this SQL:
SELECT FullName FROM Person
This gets converted to:
SELECT fullname FROM person
That is nice if you happen to like to write your queries with mixed casing.
Paul talks with Carol Keeney of BKeeney Software about databases, requirements analysis, agile/scrum and much more.