Is this the result of an SQL Injection ama namna gani wakubwa? Nimeipata pare twirra>>>>
Inahusu duplication of IDs in Garissa in the voters register
[ATTACH=full]112444[/ATTACH]
Cant be SQL injection (thats hoping you know what it means)
what am seeing here looks like an irrevocably broken and substandard data model, to me this just looks like broken constraints or lack of containts on the data model, the system should have had a unique constraint on ID number
any developer worth any semblance of being called a developer should have added a unique constraint to prevent double ID entries into the system, last i checked, no one shares an ID number with anyone else
SQL injection:confused:
I think ni selecting the wrong primary key which should be the ID
More like lotus 123 row inserts.
I thought so, no database designer allows entry of a unique value such as ID to be duplicated. That’s some shitty job there
When i said SQL Injection i meant the process used to retrieve the data
if the screen shot you have posted above is real, then they might as well have got a primary school kid to design their data model, because a standard 7 kid can do a better job than that
SQL injection IS NOT the process used to get data (query data) :D:D:D
nifundishe nielewe, hehe. Never been interested in the topic or process coz i try n design my databases safely
SQL injection is a hacking methodology that targets substandard web applications (it a broad subject but am sure you can get more details from DR. google )
i will learn hacking when i know how to build a safe system first. Nijue kwanza kujenga nyumba strong and durable ndio nijifundishe kuibomoa.
unajenga kidogo unabomoa kidogo!
A fool appears wise if he remains silent.
Learn the basics first vizuri. Foundation ndio kila kitu.
A shitty query will have such results. The Primary Key should not appear more than once.
go back to class and learn about data normalization or ask for a refund
how is a shitty query going to create duplicated id numbers, if id_number is unique ,whether you use a left, right , outer or inner joins with id schema as source, data integrity will persist, all that can happen depending on direction of join is either some blank attributes or less rows
:D:D
tuko pamoja hapo bro
Unless it was deliberate…I wouldn’t be surprised if it were.