Everything is Code
The executives at CrowdStrike testify before the US Congress, noting their software development process needs work.
2024-10-11
165 reads
The executives at CrowdStrike testify before the US Congress, noting their software development process needs work.
2024-10-11
165 reads
How simple should software development be? Steve notes it can be simple, but not too simple.
2024-10-09
185 reads
All developers hit the problem of how and where to store and set their configuration, profile, or initial data. A long time ago, it was generally decided that simple text files containing key/values were best, stored with the application. After all, you are relying on being able to entice busy people to get the permanent settings right for their requirements, folks who are generally not interested in your elegant computer science constructs. Not only that, but the settings must be parsed very quickly and efficiently, otherwise a process that uses the tool will slow to a crawl.
2024-10-04
Stored procedures can be poorly written, but Steve prefers them over embedded code.
2024-09-20
435 reads
This article looks at how you can use event sourcing to maintain persistent and asynchronous communication between microservices.
2024-09-11
Today Steve talks about how we end up with software systems that don't appear to be well engineered.
2024-08-19
205 reads
The way we approach development can have a big impact on quality, as well as how smoothly our team works together.
2024-07-19
169 reads
Steve notes that we're always better doing things better the first time. That takes some effort.
2024-07-01
166 reads
Steve doesn't have a lot of concerns about AI models writing code and reusing algorithms, but others might not feel the same way.
2024-05-29
208 reads
As a member of the PostgreSQL open-source community, I have been following the recent license change by Redis Labes on March 20, 2024. Redis introduced a dual license model, specifically adding the Redis Source Available License (RSAL), which prevents other vendors from providing Redis as a service without a paid subscription from Redis Labs. The […]
2024-04-13
167 reads
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
I set up a few users on my SQL Server 2022 instance.
CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1' CREATE USER User1 FOR LOGIN User1 GO CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2' CREATE USER User2 FOR LOGIN User2 GO CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3' CREATE USER User3 FOR LOGIN User3 GOI then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2 GO SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers