The case of Jessica Kumala Wongso garnered significant attention due to its complex and contentious nature. It began with the mysterious death of Mirna Salihin, who collapsed and died shortly after consuming a coffee at a café in Jakarta, Indonesia, in January 2016. Jessica Kumala Wongso, a close friend of Mirna, was accused of poisoning her with cyanide-laced coffee, leading to her arrest and subsequent trial. The trial unfolded with intense scrutiny from the media and the public, as well as heated debates surrounding the evidence presented. The prosecution argued that Jessica had a motive to harm Mirna due to personal conflicts, while the defense contended that there was insufficient evidence to prove Jessica's guilt beyond a reasonable doubt. The case delved into various aspects, including forensic analysis of CCTV footage, witness testimonies, and expert opinions, further complicating the legal proceedings. After a lengthy trial spanning several months, Jessica Kumala Wongso was ultimately convicted of premeditated murder and sentenced to 20 years in prison in October 2016. The case sparked widespread discussions about the reliability of forensic evidence, the integrity of legal proceedings, and the role of the media in shaping public perception. Despite the verdict, the case continues to be a subject of controversy and debate, with many questioning the fairness and transparency of the trial process. The manipulation of Café Olivier's CCTV footage through downscaling played a pivotal role in the legal proceedings of Jessica Wongso's case. Downscaling refers to the deliberate reduction of the video's resolution, from a higher resolution 1920x1080 pixels (1080P) to a lower one 960x576 pixels (960H). Throughout the trial, forensic experts, including those appointed by Wongso's defense team, revealed how this manipulation technique obscured crucial details and compromised the integrity of the evidence presented. As the trial unfolded, it became evident that the downscaling of CCTV footage significantly impacted the perception of events. The reduced resolution made it challenging for the court to discern specific actions or movements, leading to debates over the accuracy and reliability of the footage. Moreover, the discrepancies introduced by downscaling raised doubts about the prosecution's narrative and highlighted the need for comprehensive forensic analysis to uncover the truth. Ultimately, the revelation of digital tampering through downscaling became a focal point of Wongso's defense strategy. By exposing the manipulation of evidence, Wongso's legal team aimed to cast doubt on the prosecution's case and challenge the credibility of the allegations against her. The downscaling of CCTV footage emerged as a critical factor in the trial's proceedings, underscoring the importance of technological expertise and forensic scrutiny in the pursuit of justice. From my perspective, addressing an international audience, it is paramount to shed light on one of the most egregious instances of digital manipulation and tampering witnessed in recent history. This pertains to the CCTV footage from Café Olivier, which has been subjected to a series of calculated alterations by two individuals acting as digital forensic experts within the Indonesian police force: Muhammad Nuh Al-Azhar and Christopher Hariman Rianto. Their actions constitute a flagrant disregard for truth and justice, warranting a comprehensive examination to uncover the extent of their deceit and the repercussions thereof. The manipulation of CCTV footage from Café Olivier represents a brazen attempt to distort reality and obfuscate the truth. Through their purported expertise in digital forensics, Muhammad Nuh Al-Azhar and Christopher Hariman Rianto orchestrated a meticulous campaign of alteration, wherein crucial details and events within the footage were systematically tampered with or omitted altogether. This manipulation extends beyond mere technical adjustments; it undermines the integrity of the entire legal process and threatens the very foundation of justice.

Python has various database drivers for PostgreSQL. Currently, the psycopg is the most popular PostgreSQL database adapter for the Python language. The psycopg fully implements the Python DB-API 2.0 specification. The current version of the psycopg is 2 or psycopg2. The psycopg2 database adapter implemented in C as a libpq wrapper resulting in both fast and secure. The psycopg2 provides many useful features such as client-side and server-side cursors, asynchronous notification and communication, COPY command support, etc. PostgreSQL was designed to run on UNIX-like platforms. However, PostgreSQL was then also designed to be portable so that it could run on various platforms such as Mac OS X, Solaris, and Windows. PostgreSQL is free and open source software. Its source code is available under PostgreSQL license, a liberal open source license. You are free to use, modify and distribute PostgreSQL in any form. PostgreSQL requires very minimum maintained efforts because of its stability. Therefore, if you develop applications based on PostgreSQL, the total cost of ownership is low in comparison with other database management systems. In Chapter 2, you will learn querying data from the postgresql using Python including establishing a database connection, creating a statement object, executing the query, processing the resultset object, querying data using a statement that returns multiple rows, querying data using a statement that has parameters, inserting data into a table using Python, updating data in postgresql database using Python, calling postgresql stored function using Python, deleting data from a postgresql table using Python, and postgresql Python transaction. In Chapter 3, you will learn managing table structure and views including postgresql data types, postgresql create table, postgresql select into statement, postgresql create table as, using postgresql serial to create auto-increment column, identity column, alter table, drop table, truncate table, check constraint, not-null constraint, foreign key, primary key, unique constraint, managing postgresql views, creating updatable views, materialized views, creating updatable views using the with check option clause, and recursive view. In Chapter 4, you will learn statements, operators, and clauses including select, order by, select distinct, limit, fetch, in, between, postgresql like, is null, alias, joins, inner join, postgresql left join, self-join, full outer join, cross join, natural join, group by, having, intersect operator, except operator, grouping sets, cube, and rollup. In Chapter 5, you will learn postgresql trigger, aggregate, and string functions including creating the first trigger in postgresql, managing postgresql trigger, aggregate functions, avg function, max function, min function, sum function, postgresql concat function, ascii function, trim function, length function, substring function, regexp_matches function, regexp_replace function, replace function, to_number function, and to_char function.

In this book, you will create two MariaDB and PostgreSQL driven projects using PyQt. The step-by-step guide in this book is expected to help the reader's confidence to become a programmer who can solve database programming problems. A progressive project is provided to demonstrate how to apply the concepts of MariaDB and PostgreSQL using Python. In second chapter, you will learn PyQt that consists of a number of Python bindings for cross-platform applications that combine all the strengths of Qt and Python. By using PyQt, you can include all Qt libraries in Python code, so you can write GUI applications in Python. In other words, you can use PyQt to access all the features provided by Qt through Python code. Because PyQt depends on the Qt libraries at run time, you need to install PyQt. In third chapter, you will learn: How to create the initial three tables project in the School database: Teacher, Class, and Subject tables; How to create database configuration files; How to create a Python GUI for inserting and editing tables; How to create a Python GUI to join and query the three tables. In fourth chapter, you will learn how to: Create a main form to connect all forms; Create a project will add three more tables to the school database: Student, Parent, and Tuition tables; Create a Python GUI for inserting and editing tables; Create a Python GUI to join and query over the three tables. In this chapter, you will join the six classes, Teacher, TClass, Subject, Student, Parent, and Tuition and make queries over those tables. In chapter five, you will create dan configure PotgreSQL database. In this chapter, you will create Suspect table in crime database. This table has eleven columns: suspect_id (primary key), suspect_name, birth_date, case_date, report_date, suspect_ status, arrest_date, mother_name, address, telephone, and photo. You will also create GUI to display, edit, insert, and delete for this table. In chapter six, you will create a table with the name Feature_Extraction, which has eight columns: feature_id (primary key), suspect_id (foreign key), feature1, feature2, feature3, feature4, feature5, and feature6. The six fields (except keys) will have a VARCHAR data type (200). You will also create GUI to display, edit, insert, and delete for this table. In chapter seven, you will create two tables, Police and Investigator. The Police table has six columns: police_id (primary key), province, city, address, telephone, and photo. The Investigator table has eight columns: investigator_id (primary key), investigator_name, rank, birth_date, gender, address, telephone, and photo. You will also create GUI to display, edit, insert, and delete for both tables. In chapter eight, you will create two tables, Victim and Case_File. The Victim table has nine columns: victim_id (primary key), victim_name, crime_type, birth_date, crime_date, gender, address, telephone, and photo. The Case_File table has seven columns: case_file_id (primary key), suspect_id (foreign key), police_id (foreign key), investigator_id (foreign key), victim_id (foreign key), status, and description. You will create GUI to display, edit, insert, and delete for both tables as well.

In chapter one, you will learn to know the properties and events of each control in a Windows Visual C# application. You need to learn and know in order to be more familiar when applying them to some applications in this book. In chapter two, you will go through step by step to build a SALES database using Microsoft Access and SQL Server. You will build each table and add associated data fields (along with the necessary keys and indexes). The first field in the Client table is ClientID. Enter the clien ID in the Name Field and select AutoNumber in the Data Type. You define primary key and other indexes which are useful for quick searching. ClientID is a primary field. If the small lock symbol is not displayed next to the ClientID row, then you need to place it there. Right click on ClientID row and select Primary Key. A small key is now displayed next to the entry indicating it is the primary key. You will define FamilyName as an index. Select the FamilyName line. On the General tab, set the Indexed property to Yes (Duplicates OK). You then will create Ordering table with three fields: OrderID, ClientID, and OrderDate. You then will create Purchase table with three fields: OrderID, ProductID, and Quantity. And you will create Product table with four fields: ProductID, Description, Price, and QtySold. Before designing Visual C# interface, you will build the relationships between four tables. In chapter three, you will build a Visual C# interface for the database. The interface will be used to enter new orders into the database. The order form will be used to enter the following information into the database: order ID, order date, client ID, client’s first name and family name, client’s address, product information ordered. The form will have the ability to add new orders, find clients, add new clients. The completed order invoice will be provided in a printed report. In chapter four, you will build a database management system where you can store information about valuables in your warehouse. The table will have seven fields: Item (description of the item), Location (where the item was placed), Shop (where the item was purchased), DatePurchased (when the item was purchased), Cost (how much the item cost), SerialNumber (serial number of the item), PhotoFile (path of the photo file of the item), and Fragile (indicates whether a particular item is fragile or not). The development of this Warehouse Inventory Project will be performed, as usual, in a step-by-step manner. You will first create the database. Furthermore, the interface will be built so that the user can view, edit, add, or add data records from the database. Finally, you add code to create a printable list of information from the database. In chapter five, you will build an application that can be used to track daily high and low pollutant PM2.5 and air quality level. You will do this in stages, from database development to creation of distribution packages. These steps are the same as those used in developing a commercial database application. The steps that need to be taken in building Siantar Air Quality Index (SAQI) database project are: Build and test a Visual C# interface; Create an empty database using code; and Report database. The designed interface will allow the user to enter max pollutant, min pollutant, and air quality for any date that the user chooses in a particular year. This information will be stored in a database. Graphical result of the data will be provided, along with summary information relating to the maximum value, minimum value, and mean value. You will use a tab control as the main component of the interface. The control has three tabs: one for viewing and editing data, one for viewing graph of pollutant data, and another for viewing graph of air quality data. Each tab on this control operates like a Visual C# control panel. In chapter six, you will perform the steps necessary to build a SQL Server book inventory database that contains 4 tables using Microsoft Visual Studio 2019. You will build each table and add the associated fields as needed. You will have four tables in the database and define the relationship between the primary key and foreign key. You will associate AuthorID (foreign key) field in the Title_Author table with AuthorID (primary key) in the Author table. Then, you want to associate the ISBN (foreign key) field in Title_Author table with ISBN (primary key) in the Title table.

In this book, you will learn how to build from scratch a criminal records management database system using Java / MySQL. All Java code for digital image processing in this book is Native Java. Intentionally not to rely on external libraries, so that readers know in detail the process of extracting digital images from scratch in Java. There are only three external libraries used in this book: Connector / J to facilitate Java to MySQL connections, JCalendar to display calendar controls, and JFreeChart to display graphics. Digital image techniques to extract image features used in this book are grascaling, sharpening, invertering, blurring, dilation, erosion, closing, opening, vertical prewitt, horizontal prewitt, Laplacian, horizontal sobel, and vertical sobel. For readers, you can develop it to store other advanced image features based on descriptors such as SIFT and others for developing descriptor based matching. In the first chapter, you will be shown the number of devices needed to be downloaded and installed. You need to know how to add external libraries to the NetBeans environment. These tools are needed so that you can run the Java scripts. In the second chapter, you will be taught how to create Crime database and its tables. In third chapter, you will be taught how to extract image features, utilizing BufferedImage class, in Java GUI. In the fourth chapter, you will be taught to create Java GUI to view, edit, insert, and delete Suspect table data. This table has eleven columns: suspect_id (primary key), suspect_name, birth_date, case_date, report_date, suspect_ status, arrest_date, mother_name, address, telephone, and photo. In the fifth chapter, you will be taught to create Java GUI to view, edit, insert, and delete Feature_Extraction table data. This table has eight columns: feature_id (primary key), suspect_id (foreign key), feature1, feature2, feature3, feature4, feature5, and feature6. All six fields (except keys) will have a BLOB data type, so that the image of the feature will be directly saved into this table. In the sixth chapter, you will add two tables: Police_Station and Investigator. These two tables will later be joined to Suspect table through another table, File_Case, which will be built in the seventh chapter. The Police_Station has six columns: police_station_id (primary key), location, city, province, telephone, and photo. The Investigator has eight columns: investigator_id (primary key), investigator_name, rank, birth_date, gender, address, telephone, and photo. Here, you will design a Java GUI to display, edit, fill, and delete data in both tables. In the seventh chapter, you will add two tables: Victim and File_Case. The File_Case table will connect four other tables: Suspect, Police_Station, Investigator and Victim. The Victim table has nine columns: victim_id (primary key), victim_name, crime_type, birth_date, crime_date, gender, address, telephone, and photo. The File_Case has seven columns: file_case_id (primary key), suspect_id (foreign key), police_station_id (foreign key), investigator_id (foreign key), victim_id (foreign key), status, and description. Here, you will also design a Java GUI to display, edit, fill, and delete data in both tables. Finally, this book is hopefully useful for you.

This book aims to develop a database-driven desktop application that readers can develop for their own purposes to implement database-oriented digital image processing, machine learning, and image retrieval applications. In Tutorial 1, you will perform the steps necessary to add 6 tables using Visual C# into ImageProc database. You will build each table and add the associated fields as needed. In this tutorial, you will also build such a form for Officer table. This table has sixteen fields: OfficerID, FirstName, LastName, RegNumber, BirthDate, AppDate, Gender, Status, Rank, Address, Mobile, Phone, Email, Description, PhotoFile, and FingerFile). You need seventeen label controls, two picture boxes, ten text boxes, two comboxes, one check box, two date time pickers, one openfiledialog, and one printpreviewdialog. You also need four buttons for navigation, eight buttons for utilites, one button for searching officer’s name, one button to upload officer’s photo, and one button to upload officer’s fingerprint. In Tutorial 2, you will perform the steps necessary to create and implement police station form. In this tutorial, you will build such a form for PoliceStation table. This table has seven fields: PSID, OfficerID, PSName, City, Address, Phone, and Description. You need an input form so that user can edit existing records, delete records, or add new records. The form will also have the capability of navigating from one record to another. You need eight label controls, six text boxes, two comboxes, one check box, and one printpreviewdialog. You also need four buttons for navigation, eight buttons for utilites, and one button for searching officer’s name. Place these controls on the form. In Tutorial 3, you will build such a form for Accused table. This table has thirteen fields: AccusedID, FullName, MotherName, CrimeCase, BirthDate, Gender, Address, Mobile, Phone, Email, Description, PhotoFile, and FingerFile). You need an input form so that user can edit existing records, delete records, or add new records. The form will also have the capability of navigating from one record to another. You need fourteen label controls, two picture boxes, nine text boxes, two comboxes, one date time picker, one openfiledialog, and one printpreviewdialog. You also need four buttons for navigation, eight buttons for utilites, one button for searching accused’s name, one button to upload accused’s photo, and one button to upload accused’s fingerprint. In Tutorial 4, you will build such a form for Witness table. This table has thirteen fields: WitnessID, FullName, MotherName, CrimeCase, BirthDate, Gender, Address, Mobile, Phone, Email, Description, PhotoFile, and FingerFile). You need an input form so that user can edit existing records, delete records, or add new records. The form will also have the capability of navigating from one record to another. You need fourteen label controls, two picture boxes, nine text boxes, two comboxes, one date time picker, one openfiledialog, and one printpreviewdialog. You also need four buttons for navigation, eight buttons for utilites, one button for searching witness’s name, one button to upload witness’s photo, and one button to upload witness’s fingerprint. In Tutorial 5, you will build such a form for Victim table. This table has thirteen fields: VictimID, FullName, MotherName, CrimeCase, BirthDate, Gender, Address, Mobile, Phone, Email, Description, PhotoFile, and FingerFile). You need an input form so that user can edit existing records, delete records, or add new records. The form will also have the capability of navigating from one record to another. You need fourteen label controls, two picture boxes, nine text boxes, two comboxes, one date time picker, one openfiledialog, and one printpreviewdialog. You also need four buttons for navigation, eight buttons for utilites, one button for searching victim’s name, one button to upload victim’s photo, and one button to upload victim’s fingerprint. In Tutorial 6, you will build such a form for CrimeReg table. This table has fourteen fields: CRID, CRNumber, PSID, VictimID, AccusedID, DateReport, DateCrime, Arrested, CaseStatus, Description, Feature1, Feature2, Feature3, and Feature4. You need an input form so that user can edit existing records, delete records, or add new records. The form will also have the capability of navigating from one record to another. You need thirty two label controls, seven text boxes, ten comboxes, one check box, two date time pickers, six picture boxes, and one printpreviewdialog. You then need four buttons for navigation, eight buttons for utilites, and one button for searching crime register number. You also need button to save every feature.

This book aims to develop a MySQL-driven desktop application that readers can develop for their own purposes to implement library project using Visual Basic .NET. In Tutorial 1, you will build a Visual Basic interface for the database. This interface will used as the main terminal in accessing other forms. This tutorial will also discuss how to create login form and login table. You will create login form. Place on the form one picture box, two labels, one combo box, one text box, and two buttons. In Tutorial 2, you will build a school inventory project where you can store information about valuables in school. The table will have nine fields: Item (description of the item), Quantity, Location (where the item was placed), Shop (where the item was purchased), DatePurchased (when the item was purchased), Cost (how much the item cost), SerialNumber (serial number of the item), PhotoFile (path of the photo file of the item), and Fragile (indicates whether a particular item is fragile or not). In Tutorial 3, you will perform the steps necessary to add 5 new tables using phpMyAdmin into Academy database. You will build each table and add the associated fields as needed. Every table in the database will need input form. In this tutorial, you will build such a form for Author table. Although this table is quite simple (only four fields: AuthorID, Name, BirthDate, and PhotoFile), it provides a basis for illustrating the many steps in interface design. SQL statement is required by the Command object to read fields (sorted by Name). Then, you will build an interface so that the user can maintain the Publisher table in the database (Academy). The Publisher table interface is more or less the same as Author table interface. This Publisher table interface only requires more input fields. So you will use the interface for the Author table and modify it for the Publisher table. In Tutorial 4, you will perform the steps necessary to design and implement title form, library member form, and book borrowal form. You start by designing and testing the basic entry form for book titles. The Title table has nine fields: BookTitle, PublishYear, ISBN, PublisherID, AuthorID, Description, Note, Subject, and Comment. Then, you will build such a form for Member table. This table has twelve fields: MemberID, FirstName, LastName, BirthDate, Status, Ethnicity, Nationality, Mobile, Phone, Religion, Gender, and PhotoFile). You need thirteen label controls, one picture box, six text boxes, four comboxes, one check box, one date time picker, one openfiledialog, and one printpreviewdialog. You also need four buttons for navigation, six buttons for controlling editing features, one button for searching member’s name, and one button to upload member’s photo. Finally, you will build such a form for Borrow table. This table has seven fields: BorrowID, MemberID, BorrowCode, ISBN, BorrowDate, ReturnDate, and Penalty. In this form, you need fourteen label controls, seven text boxes, two comboxes, two date time pickers, and one printpreviewdialog. You also need four buttons for navigation, seven buttons for other utilities, one button to generate borrowal code, and one button to return book.