<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Kamyar Inanloo</title>
    <description>The latest articles on DEV Community by Kamyar Inanloo (@kamyar1979).</description>
    <link>https://dev.to/kamyar1979</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1452020%2Fb21b3259-f492-42c0-8761-9f2d8e429958.jpeg</url>
      <title>DEV Community: Kamyar Inanloo</title>
      <link>https://dev.to/kamyar1979</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kamyar1979"/>
    <language>en</language>
    <item>
      <title>I built a tiny Python library that turns method names into SQL queries</title>
      <dc:creator>Kamyar Inanloo</dc:creator>
      <pubDate>Fri, 29 May 2026 21:10:06 +0000</pubDate>
      <link>https://dev.to/kamyar1979/i-built-a-tiny-python-library-that-turns-method-names-into-sql-queries-1d8h</link>
      <guid>https://dev.to/kamyar1979/i-built-a-tiny-python-library-that-turns-method-names-into-sql-queries-1d8h</guid>
      <description>&lt;p&gt;I’ve been working on a small library called guess-what. The idea is simple: instead of writing boilerplate CRUD queries or repository methods, you call semantic method names and the library turns them into SQL.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;db.get_user_by_id(123)&lt;/p&gt;

&lt;h1&gt;
  
  
  SELECT * FROM users WHERE id = ?
&lt;/h1&gt;

&lt;p&gt;db.get_user_columns_name_and_email_by_status(status="active")&lt;/p&gt;

&lt;h1&gt;
  
  
  SELECT name,email FROM users WHERE status = ?
&lt;/h1&gt;

&lt;p&gt;db.add_user(user={"name": "Alice", "email": "&lt;a href="mailto:alice@example.com"&gt;alice@example.com&lt;/a&gt;", "status": "active"})&lt;/p&gt;

&lt;h1&gt;
  
  
  INSERT INTO users (name,email,status) VALUES (?, ?, ?)
&lt;/h1&gt;

&lt;p&gt;It supports:&lt;/p&gt;

&lt;p&gt;sync and async database connections&lt;br&gt;
keyword arguments&lt;br&gt;
dataclasses&lt;br&gt;
Pydantic models&lt;br&gt;
dict-based reads/writes&lt;br&gt;
simple dynamic SELECT / INSERT / UPDATE / DELETE&lt;br&gt;
stored procedure/function calls with call_...&lt;br&gt;
I’m intentionally not trying to build a full ORM like SQLAlchemy, Django ORM, or PonyORM. The goal is more like a tiny convention-based micro-ORM for simple CRUD, prototypes, scripts, admin tools, and small apps.&lt;/p&gt;

&lt;p&gt;The current API is based on naming conventions like:&lt;/p&gt;

&lt;p&gt;db.get_user_by_id(1)&lt;br&gt;
db.get_users_by_status("active")&lt;br&gt;
db.set_user_columns_status_by_id("inactive", 1)&lt;br&gt;
db.delete_user(id=1)&lt;br&gt;
I’m thinking about adding joins in a future major version, probably with names like:&lt;/p&gt;

&lt;p&gt;db.get_user_with_posts_by_id(1)&lt;br&gt;
I’d love feedback on the idea, naming conventions, and where the line should be between “useful tiny abstraction” and “oops, I accidentally rebuilt an ORM.”&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/kamyar1979/guess_what" rel="noopener noreferrer"&gt;https://github.com/kamyar1979/guess_what&lt;/a&gt;&lt;/p&gt;

</description>
      <category>database</category>
      <category>python</category>
    </item>
  </channel>
</rss>
