Author Archives: George Valentin Voina

#SQL to find dependency between tables in #Oracle database

By | February 12, 2025

There are times when we need to find which are the tables that depend on a given table. This is useful when cleanup or archiving jobs have to pe performed and the interconnection of constraints is becoming a nuisance. Lucky for us in the case of Oracle database is quite simple to search through all… Read More: #SQL to find dependency between tables in #Oracle database »

Technology fail: When #Lidl asks you to login to a #Linux terminal to find the price of an item :)

By | June 29, 2018

This was spotted in the wild by a coworker 🙂 After some research you can easily find that the device is a Scantech SG15c price scanner. See here the manual User’s Manual SG-15Plus . Interesting extract from the manual: “The login password is default blank.” Manual even gives instructions on how to modify prices 🙂… Read More: Technology fail: When #Lidl asks you to login to a… »

Best of #GDPRDay memes as mailboxes clogged today from all the #GDPR opt-in mails

By | May 25, 2018

Seeing the sheer panic and huge traffic from random sites I never remember visiting asking me for opt-in to their spam makes this a special day. Even Vodafone the big offender from my previous post Follow-up to “Vodafone #Romania and #GDPR, or how to trick customers to circumvent #GDPR”, first GDPR related fine, finally sent… Read More: Best of #GDPRDay memes as mailboxes clogged today from all… »

Follow-up to “Vodafone #Romania and #GDPR, or how to trick customers to circumvent #GDPR”, first GDPR related fine

By | May 24, 2018

Follow-up to the Vodafone case, they got owned. Vodafone was fined because of the dishonest campaign, which tried to circumvent the new GDPR regulations. See the article in romanian: Vodafone ia amendă de la ANSPDCP pentru o campanie de obținere a consimțământului pentru utilizarea datelor cu caracter personal. Basically, several people and news outlets contacted… Read More: Follow-up to “Vodafone #Romania and #GDPR, or how to trick… »