# tables Published articles for tables. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Quiz: Introduction to pandas DevFeed: [Quiz: Introduction to pandas]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-18T12:00:00Z Content type: tutorial Language: en Sources: [Real Python]() Topics: [pandas](), [CSV](), [data](), [Data Science](), [Statistics](), [Web](), [save]() Tags: [csv](), [data](), [explore](), [file](), [how-to](), [interactive](), [introduction](), [pandas](), [save](), [statistics](), [table](), [tables](), [test](), [web]() ### AI overview An interactive seven-question quiz tests core pandas skills, including reading tables from web pages, saving data as CSV, understanding DataFrames, chaining methods, and calculating statistics. ### Source excerpt Test your pandas basics: read tables from the web, save data to CSV, explore a DataFrame, and calculate averages in this interactive quiz. ## Why WCAG Conformance Doesn't Mean "Perfectly Accessible" DevFeed: [Why WCAG Conformance Doesn't Mean "Perfectly Accessible"]() Original publisher: [Read original article]() Author: Jordan Published: 2025-07-23T12:45:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Content Accessibility Guidelines](), [Accessibility](), [Web Accessibility (a11y)](), [Web](), [alt text](), [Users]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [accessible](), [alt-text](), [cause](), [content](), [lawsuit](), [markup](), [speech](), [tables](), [wcag](), [web-accessibility](), [web-content-accessibility-guidelines]() ### AI overview The article explains that WCAG conformance, including Level AA, is a valuable goal but does not guarantee a perfectly accessible experience. Pass-or-fail criteria can be met while websites still create barriers through poor alt text, difficult captions, incomprehensible table presentation, or layout shifts caused by slow page speeds. ### Source excerpt The Web Content Accessibility Guidelines (WCAG) are an excellent set of standards, and WCAG conformance is achievable -- regardless of the size of your website, the complexity of its features, or any other factors. ## Getting comfortable with psql DevFeed: [Getting comfortable with psql]() Original publisher: [Read original article]() Author: Map Published: 2024-11-11T15:57:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [Command-line interface](), [Database]() Tags: [cli](), [commands](), [config](), [database](), [pager](), [postgres](), [psql](), [query](), [tables](), [timing](), [vim]() ### AI overview A practical introduction to getting comfortable with psql, the PostgreSQL command-line interface. It covers utility commands, describing tables, configuration options, query timing, output formatting, pager settings, and editing queries with an external editor. ### Source excerpt psql is a CLI editor that ships with Postgres. It's incredibly powerful for working with Postgres, and doesn't take too much of a learning curve to start to get comfortable so you can really feel like an expert working with your database. Just a rundown of a few things to get you started: Once connected in psql you can get an idea of all utility commands available with: \? A handy thing I use all the time is \d. \d will describe the tables within database. You can also add a table/index/etc. onto it to describe that specific table such as: \d accounts There are a number of options you can set in your psqlrc (config) file to customize your CLI experience. But you can also toggle those when directly working in psql. \timing will give you the time it took to run your query \x auto will autoformat your text output \pset pager 0 turns off your pager or 1 to turn it back on Oh and for editing a query in your editor of choice. Make sure you set your $EDITOR enviroment variable to the editor of your choice, though the only right choice is vim: \e Just a few things to get you started working with psql. Your browser does not support video ## HTML Tables with Horizontal Scroll and Sticky Headers DevFeed: [HTML Tables with Horizontal Scroll and Sticky Headers]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2024-10-09T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [HTML](), [Web Development](), [modern web development]() Tags: [container](), [css](), [design](), [dockerignore-usage](), [example](), [headers](), [helps](), [html](), [javascript](), [table](), [tables]() ### AI overview A tutorial on building HTML tables that support horizontal scrolling and sticky headers. It explains why sticky positioning can fail inside an overflow container and presents a table-wrapper height as the solution, producing a vertically and horizontally scrollable datagrid-style view. ### Source excerpt Turns out, creating an HTML table that has both horizontal scroll and fixed headers can be a tricky problem. As another developer said about... ## My SQL Bad Habits DevFeed: [My SQL Bad Habits]() Original publisher: [Read original article]() Author: Map Published: 2013-05-26T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [SQL](), [syntax](), [JOIN](), [ordering]() Tags: [implicit-joins](), [ordering](), [postgres](), [query](), [sql](), [syntax](), [tables]() ### AI overview The author discusses personal SQL bad habits that can make queries less clear or more error-prone. The article covers ordering or grouping by column numbers, implicit joins, insufficient comments, and manually generated lists used for filtering. ### Source excerpt I'm reasonably proficient at SQL - a coworker when pseudocoding some logic for him pointed out that my pseudocode is what he thought was executable SQL. I'm fully capable of writing clear and readable SQL - which most SQL is not. Despite that I still have several bad habits when it comes to SQL. Without further adieu heres some of my dirty laundry so hopefully others can not make the same mistakes. Order/Group by Column Numbers When quickly iterating on a query its a lot less typing to put the column number as the thing you want to order by. Here's a quick lightweight example: SELECT email, created_at FROM users ORDER BY 2 DESC LIMIT 5; This gives me my last 5 users that have signed up for my site. Of course as soon as I have this I may want to add some data to it, like their first name so I can send them a welcome email. I quickly alter the query to: SELECT email, first_name, created_at FROM users ORDER BY 2 DESC LIMIT 5; And now I have 5 users that have signed up ordered by their first name. Sure its obvious when you have 1 column you're ordering by, but when you have GROUP BY 1, 2, 3, 4, 5, 6 which is actually open in one of my tabs currently its a bit more confusing.... Though if you really want to have some fun, share a query with someone that looks something like this: SELECT email as "3", first_name "2", created_at "1" FROM users ORDER BY "1", "3" DESC LIMIT 5; Implicit Joins I seldom use the syntax INNER JOIN. Instead I simply put the two tables in my where clause and ensure I have a where condition. The problem with ensuring I have a where condition is sometimes I don't, especially when you're dealing with 3 tables. SELECT email, product.name, product.price FROM users, orders, items WHERE users.id = orders.user_id AND orders.id = items.order_id Is less clear (especially when dealing with 5-6 tables) than the alternative: SELECT email, product.name, product.price FROM users INNER JOIN orders on users.id = orders.user_id INNER JOIN items on orders.id = items.or ## ActiveObjects streaming API DevFeed: [ActiveObjects streaming API]() Original publisher: [Read original article]() Author: Alex Hennecke Published: 2011-09-30T03:28:25Z Content type: release Language: en Sources: [Atlassian Developer Blog]() Topics: [API]() Tags: [allows](), [api](), [greenhopper](), [jira](), [performant](), [plugins](), [reading](), [tables]() ### AI overview The article announces a new ActiveObjects API for performant reading of large tables. ### Source excerpt New API for ActiveObjects allows performant reading of large tables