Sicurezza Nazionale a Rischio: La Violazione dei Dati della Polizia Nazionale del Paraguay Scuote il Paese

Più di 500.000 #documenti interni e immagini, nonché 175 GB di #database #SQL, sono stati rubati dal #sistema della Polizia Nazionale del #Paraguay (Policía Nacional del Paraguay).

A causa della presenza di #informazioni di identificazione personale (#PII), come fotografie di detenuti e resoconti di incidenti, i #dati sono disponibili solo a giornalisti e #ricercatori.

#redhotcyber #online #it #web #ai #hacking #privacy #cybersecurity #cybercrime #intelligence #intelligenzaartificiale #informationsecurity #ethicalhacking #dataprotection #cybersecurityawareness #cybersecuritytraining #cybersecuritynews #infosecurity

https://www.redhotcyber.com/post/sicurezza-nazionale-a-rischio-la-violazione-dei-dati-della-polizia-nazionale-del-paraguay-scuote-il-paese/

@tuckerteague 😆 since this is getting a lot of boosts, I WILL also say that on the current project I'm on, with a thoroughly microservices architecture, we're NOT using PostgreSQL (or any relational db -- datastores are primarily mongodb/DocumentDB), and in this case it feels appropriate.

#PostgreSQL #SQL #mongoDB #noSQL

@tuckerteague at the base level of just-learning-SQL, PostgreSQL will do the same basic SQL CREATE-SELECT-UPDATE-DELETE stuff as any other DB in mostly the same ways, honestly. So if that's your only goal, PG is as-good as anything else, and you might as well keep going there if you've already started; or switch, whichever.

But as you dig deeper, PG has more underlying depth and consistency under the surface than other systems. Its type system is both more rigid and extensible than MySQL's, for example. There is support for various languages for server-side procedures, it has a complete ecosystem for building custom extensions, and so on.

In short, in PG, you can peel away the layers and find surprisingly strong and consistent reasoning underneath, instead of a nightmare of patched-over bad decisions, which you might find elsewhere.

Note: I am an avowed PostgreSQL fanboy, so, take any grains of salt you'd like.

#SQL #PostgreSQL

@tuckerteague PostgreSQL is the go-to datastore on almost ALL projects I've been on for the last 10 years... or more.

It's awesome. Frankly, for *almost* all purposes where people are using these hip NoSQL, timeseries, geospatial, etc things and whatnot, at the scale 99% of us need, pg will handle it JUST fine. Seriously.

And as others have said, very solid but also VERY powerful.

#PostgreSQL #SQL

@adrienne
Had a busy day in the #SaltMine yesterday. I did finally figure out my #SQL problem and was very excited. Google was no help at all. And now I have another small project, to figure out what reporting package to use. The guy who wrote the system has used Crystal Reports in the past, but it isn't compatible with .Net 7, so we need to find another solution. Any recommendations out there?

You can't run Databases on Kubernetes!!!

Or can you ???
Find out, when Mattias presents VMware Data Services in our next Tanzu CNA webinar on tuesday.
https://webinars.tanzu.dk
#Tanzu #Rabbitmq #SQL #Kubernetes

https://www.plutora.com/blog/natural-language-queries-explained - #SQL + #ChatGPT = #NQL: Natural Query Language. Just ask the machine about the data you want ... presuming the schema is ok and the columns are named well.

Put in a full day at the #SaltMine yesterday, mostly going over the #Blazor code. Definitely a complicated stack and hard to figure out where to put the logic. Currently, much of it is in SQL stored procedures, but there are plenty of drawbacks with that, like no versioning and hard to find the code. I'm trying to do some tricky #SQL searching to make it easier to find records but the syntax keeps tripping me up.

My #SQL style guide. https://www.linkedin.com/pulse/bizoneness-steves-style-guide-sql-queries-sap-b1-steven-lipton?utm_source=share&utm_medium=member_ios&utm_campaign=share_via

The problem with writing a complicated #SQL query is you need a /more/ complicated one to validate the results. 🙄

Wednesday Links - Edition 2023-09-06
https://dev.to/0xkkocel/wednesday-links-edition-2023-09-06-1ip
#java #jvm #virtualthreads #reactor #profiling #latency #gradle #sql #devops

Would appreciate some feedback from developerland, folks. Please boost for wider views? 🙏

Back-End / Full-Stack Developers - how would you describe your SQL querying skills (based on your strongest relational or non-relational database)?

#dotnet #java #php #python #nodejs #developer #database #sql

I officially finished to write the #backened of my web application for my #CS50 final project.

What a ride, in hindsight just a few months ago a couldn't believe I was gonna be able to design and build an app from scratch like this.

Now, on to the #frontend.

#python #flask #sql

A recent "study" says #python and #SQL are the most popular/required programming languages for 2023. Looking at the work I have been doing lately, it seems I am trending.

Has anyone ever thought of putting some order in #WordPress #sql queries? To insert one post in #bbPress, wordpress does more than 100 sql queries. I've seen queries with litteraly 1000s of items in the IN clause! I allways knew it was bad, but I couldn't imagine it's that bad #php #mysql

Ох какой прекрасный срач в комментах: https://www.opennet.ru/opennews/art.shtml?num=59499

Старперы и неосиляторы-лошки взъелись на язык #PRQL, который должен наконец прийти на замену замшелому #SQL или хотя бы стать альтернативой.

Думаю может написать статейку на хабр, где привести примеры когда SQL реально неудобен и нечитаем, а PRQL прям вывозит.

If you are wondering what the future of #databases looks like, you might be interested in this article https://doi.org/10.14778/3603581.3603604

The authors argue that despite increasing specialization, databases share the same components. By relying on standards, you can develop a composable system with:
- your preferred language interface (#SQL, #Ibis, #dplyr, ...). The query is converted into an intermediate representation (like #substrait)
- a query optimizer
- an execution engine
- an execution runtime

Well, I think it could be nice to talk a bit about myself, so here it goes (it is a long one, be warned)

My (still ongoing) journey from engineering to programming: Prologue
As can be seen in my profile bio, my name is Iago Andrade, and I am a Brazilian. What can't be seen there, though, is that I'm a mechanical engineer, and I have worked as a mechanical designer since 2018. This year (2023) I decided to pursue an old desire, which was to be able to work with #programming.

First contact
From the very first year at university, I fell in love with programming, when we were introduced to #C. Most of my friends were not really interested in that, and thought it was too difficult, but I was fascinated by the possibilities of what could be done with it.
At first, we used it mostly to solve dificult mathematical problems through iterative process, but my curiosity led me to learn more than just what was taught in classes. We were also later introduced to MATLAB and EES, and I even learned a bit of #Python in order to help a friend of mine.
But as the course became more and more time consuming, I started to drift away from that passion, and focus more on the other disciplines, and only sparingly did I delve into anything related to programming.

First job
As I graduated, I soon got a #job in mechanical design, modeling industrial equipment and parts and its drafts for production. As I had little time for studying, programming was put aside for a while, and all the focus was put into this job.
I learned a lot at this job, and managed to build a lot of resources for accelerating, and even automating tasks, and that kept me reminded of how much I liked to solve problems like these. I even got to the point of learning some #bash script in order to automate the creation of folders in the company's server (which did not end up very well, due to the lack of some quotes hehe). Though the script caused some problems, it was solved in the end (and I learned the important lesson of debugging everything very thoroughly).

Reigniting an old passion
At some point between then and now, I learned of the existence of a "new" game engine called #Godot. I had never made any #games, and had never used a game engine before either, but I had had some contact with #FOSS (free and open source softwares), like #blender and #inkscape, and that one caught my attention, since I had always wanted to create games. Since it was free, super lightweight, I decided to give it a go. It felt so good to learn that tool, and programming in it reminded me of how much I liked to code.
Back then, a friend of mine was also interested in making a game, and he wanted to be more focused on the story part of it, which was perfect since I wanted to focus on the programming and possibly the art and music for it. We started to work on the idea, got a ton of references, and started building the overall scope and story, until one day we lost momentum and just couldn't get back to it. Our jobs were sucking too much energy, and we decided to put it aside until we had more time to do it properly.

#SQL and the leap of faith
After some more years of working with 3D modeling, the company where I was working decided to implement an ERP system. The problem was they didn't have anyone from the inside who was qualified for some of the tasks that would appear, and they tasked me with dealing with those problems.
I had never worked with an ERP system, but had some idea of how #databases worked, and that helped a lot in making some decisions early on (like not entrying all data manually). I had to learn how to bulk clean old data from another system they had used before, which had been fed by many different people, with a lot of mistakes and inconsistencies.
After that, I had to import all that data into the system, and I decided it was time to learn SQL so I could query the database properly when I needed information. And that once again triggered my interest in programming, leading to my decision to make new templates for the engineering team.
These templates used programming for automating some of the tasks, in a language specific for the modeling software,reducing many of the steps in the project pipeline, and making it easier to input new equipment in the system.
As I became more and more #tired of some problems at work, and got more interested in programming again, I made the decision of focusing in relearning the languages I had contact with, and while searching for resources, I was informed that #Harvard offered this course online, called #CS50
For a few months I tried, and was unable to #study in my spare time. So ultimately, I decided to #quit my job, finish CS50, and start a career in programming.

Paying the #bills
With only the final project from the course left, money was running short, and bills were still appearing, so I had to start looking for jobs, and I ended up getting another job in mechanical design. The difference now is that it is much closer to home, so I will be able to finish my final project on my spare time, and keep looking for #junior roles in programming.

Epilogue: The Final Project
Since this toot is ridiculously long already, I may as well talk about the final project for whoever got to this part haha
The idea for the project is to mix a bit of #gamedev with #webdev, making a site with three main areas containing mini-games in three different styles, from #ASCII to one with actual graphics. If all goes well, I also wanted to enable players to get a score, and keep that in a database, if the player so desires. #Backend is being done in python with #flask, #frontend is using templates from flasks #jinja, but mostly plain #HTML #CSS and #javascript

A few weeks ago, I took a deep dive into SQL queries in order to review it and finish up some data analytics projects I started a while ago.

This blog post is a quick start guide to SQL queries for those who are just getting started with them.

In it, I discuss how to use the SELECT, FROM, WHERE, GROUP BY, and ORDER BY reserved words. Including code snippets and examples using Google's Big Query.

Follow the link to read more: https://blog.ananfito.dev/quick-start-guide-to-sql-queries

#LearnInPublic #SQL #CodeNewbies

Microsoft SQL servers hijacked to deliver Cobalt Strike and ransomware | TechRadar https://www.techradar.com/pro/security/microsoft-sql-servers-hijacked-to-deliver-cobalt-strike-and-ransomware #microsoft #sql #ransomware