lukesrw / sql-converter Goto Github PK

View Code? Open in Web Editor NEW

0.0 1.0 0.0 134 KB

Easily convert between SQL, JS, and PHP

Home Page: https://sql.lukesrw.co.uk

JavaScript 1.77% CSS 0.16% TypeScript 98.07%

better-sqlite3 converter javascript js mysql2 parse parser php sql

sql-converter's Introduction

SQL Converter

Online Converter

Usage

Using the converter you can quickly swap between writing application JS/PHP code and database SQL queries.

Want to try your query with different values? Slow debugging in-application? Paste the code and use SQL directly.

Once you're happy that the updated SQL works, copy the JS/PHP back into your application and get back to work!

Setup

If you want a copy to make changes or use the tool locally, you can clone the repository:

git clone [email protected]:lukesrw/sql-converter.git

Then run the Next.js development server:

npm run dev
# or
yarn dev
# or
pnpm dev

You can make your own modifications to the tool by updating /src/app/page.tsx.

If you build a fantastic feature make sure to pull request it, so others can see your contributions.

sql-converter's People

Contributors

Watchers

sql-converter's Issues

Add error handling for sql-formatter

Attempting to format with invalid SQL currently results in:

If sql-formatter provides end-user useful error messages then this should also be displayed somewhere.

Update README

Prior to open sourcing I need to update the README with useful information.

Purpose
Usage
Installation
Video Demo?

Hyphens not properly parsed by JS/PHP editors

Add Vercel analytics

https://vercel.com/docs/concepts/analytics/quickstart

Update Column.tsx to use twMerge

If the className prop isn't used it currently leaves "undefined" in the class

Escaped queries aren't properly parsed

For example, PHP:

$query = $Database->query(
    'SELECT
		*
    FROM
		TableName
	WHERE
		TableName.FieldName = \'Test\''
);

Results in, SQL:

SELECT
	*
FROM
	TableName
WHERE
	TableName.FieldName = \

Language Variable Overrides

Currently conversion to other languages maintains the variable value, for example PHP:

$query = $Database->prepare(
    'SELECT * FROM TableName WHERE ColumnName = :Foo'
);

$query->execute(array(
    ':Foo' => $FooValue
));

Is converted into SQL:

SET @Foo = '$FooValue';

SELECT * FROM TableName WHERE ColumnName = @Foo

If you were to change the @Foo = '$FooValue' to test the query, for example @Foo = 'Test', the PHP would update as:

$query = $Database->prepare(
    'SELECT * FROM TableName WHERE ColumnName = :Foo'
);

$query->execute(array(
    ':Foo' => 'Test'
));

A useful feature would be the ability to lock-in variable values that are specific to the language.

In this case, I could've set that regardless of the other textareas the PHP value should always be $FooValue.

PHP Variable Quotes

Pasting the following PHP into the textarea:

$query = $Database->prepare(
    'SELECT * FROM TableName WHERE ColumnName = :Foo'
);

$query->execute(array(
    ':Foo' => $Test
));

Is parsed properly, but reads back as:

$query = $Database->prepare(
    'SELECT * FROM TableName WHERE ColumnName = :Foo'
);

$query->execute(array(
    ':Foo' => '$Test'
));

Variable values in the PHP output should not be quote escaped if they begin with a dollar sign.