#SQL Developer

[internaciarekruto]

THINKWISE DEVELOPERS for #Europe, REMOTE WORK

THINKWISE DEVELOPERS for #EuropeREMOTE WORKContract : 6 MonthWages : 50 EURO Per HrSkill : #DotNet #SQL #thinkwisedevelopers DotNet #dotnetdeveloper #dotnetdevelopment #DotNetDevelopersinEurope europe #europejobs #jobsineurope #itjobsineurope #european #indianineurope #europerecruitment #itrecruitment #itstaffing openfornewopportunities #jobopenings #hirirng #hiringalert #hiringimmediately…

[hiredevelopersdev]

SQL Developer Skills with Databases

SQL Developer Skills with Databases encompass a range of abilities required to effectively work with databases using Structured Query Language (SQL). These skills include proficiency in writing SQL queries, designing and optimizing database schemas, implementing database security measures, and conducting data analysis. SQL developers should also be well-versed in database management systems (DBMS) such as Oracle, MySQL, or SQL Server. Strong problem-solving and troubleshooting skills are crucial for resolving database-related issues. With these skills, SQL developers can efficiently manipulate and extract data, ensure data integrity, and contribute to the successful development and maintenance of databases for various applications and industries.

Read more:- SQL Developer

[scaleracademy]

Brush up on your SQL coding skills with this comprehensive list of the most commonly asked SQL Queries at top companies.

[hayacode]

Software Development using C# (Bootcamp)

Week 6 done ✨ Almost halfway through the bootcamp 🥳

We started the backend project last week, this project is a teamwork and each team has 5 students. Honestly, I was scared of it because being the only one with a biology degree in a whole class of tech students made me overthink how will I do in teamwork and how I will definitely screw up everything and it’s true I made so many mistakes as expected (today lesson the hardest orz) but i am so glad my team members are so kind and they help me a lot 🥹

What i have learned from the bootcamp in the past 2 weeks 💻

- Database

- Data modeling 

- Relationship: 1-1, 1-M, M-M

- REST architecture

- HTTP methods & status codes

- Introduction to ASP.NET Core

- Webapi template & Swagger

- Create endpoints for CRUD operations

- Handle & return  error in webapi

- Using controller and service folder with dependency injection

- Authentication & Authorization (role base) 

- Introduction to ORMs

- Relations in EF Core

- Config database with Npgsql

(Yes, all of this in 2 weeks sobbbs)

Now let’s talk about C# again

- i am 50% done with codecademy course

- I Finished Bro Code C# videos (highly recommended and I plan to watch his React videos soon)

I am also almost done with my React first course ✨

Oh yeah Last but not least, this bootcamp gives us career advice classes related to developers' jobs, interviews, and how to have a good CV, LinkedIn, and github (if you are a friend on Discord, dm me so I can send you all the amazing stuff 💫)

[codingquill]

SQL Fundamentals #1: SQL Data Definition

Last year in college , I had the opportunity to dive deep into SQL. The course was made even more exciting by an amazing instructor . Fast forward to today, and I regularly use SQL in my backend development work with PHP. Today, I felt the need to refresh my SQL knowledge a bit, and that's why I've put together three posts aimed at helping beginners grasp the fundamentals of SQL.

Understanding Relational Databases

Let's Begin with the Basics: What Is a Database?

Simply put, a database is like a digital warehouse where you store large amounts of data. When you work on projects that involve data, you need a place to keep that data organized and accessible, and that's where databases come into play.

Exploring Different Types of Databases

When it comes to databases, there are two primary types to consider: relational and non-relational.

Relational Databases: Structured Like Tables

Think of a relational database as a collection of neatly organized tables, somewhat like rows and columns in an Excel spreadsheet. Each table represents a specific type of information, and these tables are interconnected through shared attributes. It's similar to a well-organized library catalog where you can find books by author, title, or genre.

Key Points:

Tables with rows and columns.

Data is neatly structured, much like a library catalog.

You use a structured query language (SQL) to interact with it.

Ideal for handling structured data with complex relationships.

Non-Relational Databases: Flexibility in Containers

Now, imagine a non-relational database as a collection of flexible containers, more like bins or boxes. Each container holds data, but they don't have to adhere to a fixed format. It's like managing a diverse collection of items in various boxes without strict rules. This flexibility is incredibly useful when dealing with unstructured or rapidly changing data, like social media posts or sensor readings.

Key Points:

Data can be stored in diverse formats.

There's no rigid structure; adaptability is the name of the game.

Non-relational databases (often called NoSQL databases) are commonly used.

Ideal for handling unstructured or dynamic data.

Now, Let's Dive into SQL:

SQL is a :

Data Definition language ( what todays post is all about )

Data Manipulation language

Data Query language

Task: Building and Interacting with a Bookstore Database

Setting Up the Database

Our first step in creating a bookstore database is to establish it. You can achieve this with a straightforward SQL command:

CREATE DATABASE bookstoreDB;

SQL Data Definition

As the name suggests, this step is all about defining your tables. By the end of this phase, your database and the tables within it are created and ready for action.

1 - Introducing the 'Books' Table

A bookstore is all about its collection of books, so our 'bookstoreDB' needs a place to store them. We'll call this place the 'books' table. Here's how you create it:

CREATE TABLE books ( -- Don't worry, we'll fill this in soon! );

Now, each book has its own set of unique details, including titles, authors, genres, publication years, and prices. These details will become the columns in our 'books' table, ensuring that every book can be fully described.

Now that we have the plan, let's create our 'books' table with all these attributes:

CREATE TABLE books ( title VARCHAR(40), author VARCHAR(40), genre VARCHAR(40), publishedYear DATE, price INT(10) );

With this structure in place, our bookstore database is ready to house a world of books.

2 - Making Changes to the Table

Sometimes, you might need to modify a table you've created in your database. Whether it's correcting an error during table creation, renaming the table, or adding/removing columns, these changes are made using the 'ALTER TABLE' command.

For instance, if you want to rename your 'books' table:

ALTER TABLE books RENAME TO books_table;

If you want to add a new column:

ALTER TABLE books ADD COLUMN description VARCHAR(100);

Or, if you need to delete a column:

ALTER TABLE books DROP COLUMN title;

3 - Dropping the Table

Finally, if you ever want to remove a table you've created in your database, you can do so using the 'DROP TABLE' command:

DROP TABLE books;

To keep this post concise, our next post will delve into the second step, which involves data manipulation. Once our bookstore database is up and running with its tables, we'll explore how to modify and enrich it with new information and data. Stay tuned ...

Part2

[crackaddict55]

Ok turns out if you don’t practice your problem solving skills often there is a 100% chance your brain will regress to the state of your 6 year old self and you will forget how to solve the most basic problems.

Good to know.

[mechanical-moron]

Programmers, Web designers, game developers, anyone else who does stuff with numbers on a computer screen.....curious to know if you guys ever dream in code, and if so, do you like it? I for one do not find it to be particularly enjoyable but want to hear what others have to say lol.

[bf-rally]

today i tried to code more

[scvnthorpe]

That time I restored a Database view

Recently at work we've been migrating an old database system to a new platform to save money - this kind of shit is what makes your business processes faster, cheaper and more correct - and this has entailed sifting through a lot of tables, views, and views made of tables and views!

As it happens the finance guy who does all the payroll and expenses is a great guy to work with and basically the one person who knows all the relevant business rules, but also basically treats databases like they're excel workbooks. As such you have a bunch of bits stitched to each other and we're just figuring out how to first move everything and then ease into a well-oiled relational model with no duplication and all together on a single database.

While we in the dev team were figuring out how to do this for finance we were recently testing out a modified version of a view built on top of the old version and accidentally deleted the old version and not the modified testing version.

Mistakes are bound to happen, but we needed to figure out how to either restore it or at least figure out how to work without it because finance people love their data views and reports. There are probably clever things you can do with any DBMS to find shit you just dropped and restore it from backup, but I then realised that I'd been tasked with generating all the scripts for the database objects. There had to be a script laying around!

Sure enough I went to dig up the build script for the dropped view, and I ran it.

I queried it, and everything was back in place.

Shit goes wrong sometimes, but having the right failsafes can really make a difference.

Script your shit, use backups, use version control!

[forever-stuck-on-java-8]

so it turns out they weren't kidding when they said breaking a monolith into microservices is hard.

[hexaredecimal]

Making a compiler

Every programmer out there, new or experienced longs for a chance to create their own programming language and compiler. I am no exception. Months ago I decided to fork an old project on github and develop it in my image. The project was a golang-like unfinished compiler, so I dug in and made changes. I changed the language to resemble a subset of rust, go and ocaml. I plan to add a LLVM backend inspired by the tre golang compiler. I will continue working on it until it kinda works. I still have a lot to do. check out the project on the link below. If you want to contribute submit a pull request.

[autogeneity]

also I asked for a sample response from the pending service and received possibly the most wack API I've ever seen.

it takes. an entire raw SQL query. as a url parameter.

[small-basic-programming]

My 365 Days Streak at MIMO ...

"At Mimo, we believe that coding can open doors to opportunities like few other skills. That's why we've rallied around the purpose of making coding accessible to as many people as possible." MIMO

Today I completed my 365 day streak at Mimo. Phew, that was a long way through the programming and scripting languages “Python”, “SQL”, “HTML”, “CSS” and “JavaScript”.

Even though there were sometimes tough times and I often repeated certain course sections, e.g. with "JavaScript", and the progress wasn't immediately apparent, I still enjoyed learning with MIMO again and again.

The support is also good, if you have questions or just get stuck. I can recommend MIMO to anyone who wants to immerse themselves in the world of programming languages online or with the app.

Post #209: Whoopee! My 365 Day streak on Mimo happens today on March 3, 2024.

[hayacode]

Bootcamp week 5 - day one <datebase> ✨

[codingquill]

SQL Fundamentals #2: SQL Data Manipulation

In our previous database exploration journey, SQL Fundamentals #1: SQL Data Definition, we set the stage by introducing the "books" table nestled within our bookstore database. Currently, our table is empty, Looking like :

books

| title | author | genre | publishedYear | price |

Data manipulation

Now, let's embark on database interaction—data manipulation. This is where the magic happens, where our "books" table comes to life, and we finish our mission of data storage.

Inserting Data

Our initial task revolves around adding a collection of books into our "books" table. we want to add the book "The Great Gatsby" to our collection, authored F. Scott Fitzgerald. Here's how we express this in SQL:

INSERT INTO books(title, author, genre, publishedYear, price) VALUES('The Great Gatsby', 'F. Scott Fitzgerald', 'Classic', 1925, 10.99);

Alternatively, you can use a shorter form for inserting values, but be cautious as it relies on the order of columns in your table:

INSERT INTO books VALUES('The Great Gatsby', 'F. Scott Fitzgerald', 'Classic', 1925, 10.99);

Updating data

As time goes on, you might find the need to modify existing data in our "books" table. To accomplish this, we use the UPDATE command.For example :

UPDATE books SET price = 12.99 WHERE title = 'The Great Gatsby';

This SQL statement will locate the row with the title "The Great Gatsby" and modify its price to $12.99.

We'll discuss the where clause in (SQL fundamentals #3)

Deleting data

Sometimes, data becomes obsolete or irrelevant, and it's essential to remove it from our table. The DELETE FROM command allows us to delete entire rows from our table.For example :

DELETE FROM books WHERE title = 'Moby-Dick';

This SQL statement will find the row with the title "Moby-Dick" and remove it entirely from your "books" table.

To maintain a reader-friendly and approachable tone, I'll save the discussion on the third part of SQL, which focuses on data querying, for the upcoming post. Stay tuned ...

[melonpond]

Khan academy save me.

save me khan academy

khan academy...