txtSQL

Congratulation for the nice work on the parser in the 4.0a version.

I was looking for a PHP sql parser but couldn't find one.

Chances are I'll try do hacking on it in the next weeks.

Points I don't like too much:
* _args array is good, an object structure would be much better and help you extend the parser further.
* you lack a public method (very easy to implement anyway) to return parsing result. That forces user to extend your class, which is not always the best choice.
* you should put togheter some unit tests.

IMHO you should try to threat sql parser as a separate package. That way you could attract interest from a wider range of users. (one could use it to add power existing active record classes for example).

Looking forward for join support. Good work!

Thanks for the compliments... makes me feel good

But anyways, those are some good points you make and I agree with all of them...

I was also thinking that I allow the parser as a separate download because I was in need of one before I created my own... but none exist for PHP that were around. It's just that there's so much to do with this project of mine, and I'm the only person that is working on it (I still have to finish the script, create docs, update the txtSQLAdmin script and offer some more small sample scripts).

In regards to JOINS, I have implemented INNER JOINS (explicit and implicit) and am on route to devising an efficient OUTER JOIN algorithm... though it's gonna be an alpha release, I still want to have as stable a file release as possibly possible the first time around

I downloaded 4.0 code file-per-file, from the 4.0 development section of the site, and the parser wasn't able to handle innerjoin, nor any other kind of join.

I am not talking about storage engine, I am talking about ->parse( 'selec..' ); query returning error and false when trying a join.

You can find a sample here:
http://www.stefanoforenza.com/parser/test.php

Putting toghether the code for join support in the parser is not trivial but not so hard too.

Beside that, as note/bug report, the parser doesn't support multiple order by clauses ( order by surname, firstname ).

Looking forward for next releases. See you

I haven't uploaded the updated tokenizer and lexer codes for JOINS, partly because they aren't fully implemented yet... but as you said, they aren't hard to implement, only a few lines of code... I should upload the new code sometime today.

but the orderby clauses SHOULD work, so long as each column sort-direction is specified ...

so

ORDER BY id ASC, name DESC, age ASC ...

OK, I've updated the tokenizer and lexer codes (and also changed quite a few things in all four files actually)...

You can find the updates in the development section. Hopefully this won't take too much longer, I have to manage school and programming just right...

FarazAli wrote:OK, I've updated the tokenizer and lexer codes (and also changed quite a few things in all four files actually)...

You can find the updates in the development section. Hopefully this won't take too much longer, I have to manage school and programming just right...

Thank you very much. I'll give it a try soon.

C U

Stefano

http://www.fashion-products.com [url=http://www.fashion-products.com ]is a sell air force one,
air jordan,bape,kicks,nike,Jerseys,Shoes,Clothing,Bag,Glasses,Caps&Hats,sneakers,sunglasses,
watches,Jewelry,Electronics,NBA,NFL,NHL,MLB[/url]
shoes
clothing
Handbags Wallets
Hat
Sunglasses
Belts
Watches
Jewelry