txtSQL

Hi!

I'm very curious about this project and really want to start using it. But it seems dead? Is it?

Have a great one!

Cheers...

Heh, I see now that it does'nt seems dead.. Great news for me.. Looking forward to 4.0...how is the work progressing?

It's rather slow right now, I'm almost done with Undergraduate study here at Rutgers. But I'm also busy with MCAT's and finals right now. I've actually been looking for a partner who will help txtSQL grow; someone who knows their programming and share the same ideas I do...

but until then, work will probably remain relatively slow. I'm sorry, I'm only one person. When the project is done, it will be well worth the wait.

I would be happy to help you with development on txtSQL 4.0. While my own flat file database script didn't go to plan because of problems with the back end, I managed to implement a fairly sound basic SQL parser that was designed to work with any php database application, and all you have to do is specify a few callback functions and then the SQL parser will get to work. If you want I could show you the code and then we could integrate it with your parser (it hasn't got features such as JOINS and still lacks support for proper types (CHAR, VARCHAR etc.). I could also help you out with the documentation.

Sorry the delay in response... I've been up to my head with so much work and chaos, it's been hard to find time.

Anyways, so you're interested in working with txtSQL? I'm definitely glad to hear that, I can use all the help I can get. You should email me, and we'll work something out from there.

Email sent

scross wrote:I would be happy to help you with development on txtSQL 4.0. While my own flat file database script didn't go to plan because of problems with the back end, I managed to implement a fairly sound basic SQL parser that was designed to work with any php database application, and all you have to do is specify a few callback functions and then the SQL parser will get to work. If you want I could show you the code and then we could integrate it with your parser (it hasn't got features such as JOINS and still lacks support for proper types (CHAR, VARCHAR etc.). I could also help you out with the documentation.

Scross,
my British North Sea neighbour. (I live in Sweden)

I long to see both your FFD and ICMS arrive in a published state.
Bit disappointed when visit your site and there's nothing coming.
Because I am sure your stuff, coding and way of designing for web with PHP
is well inline with my own thinkings.


I have past weeks done research for SQL Parsers scripts in PHP.
I think I have gotten the overall picture.

PHP Projects Aiming to Parse SQL Query.

• Ali Faraz txtSQL 4.0, SQL parser + lexer classes.
  Very promising, but not much work done. Unfortunately!
  
• Pear SQL_Parser, last release 2004, but CVS has got recently updated file versions.
  Lexer uses ctype lists and this SQL Parser has option of SQL DIALECTS!
  To begin with two dialect files: ANSI SQL and MySQL SQL dialects.
  The roadmap is to use EBNF expressions (a format to define language structure).
  I say this is currently the most advanced and most ambitious project in PHP,
  if judge by existing and planned features. But not much work done.
  
• Your own Scross fSQL, of what I so far know nothing much.
  
• My own SQL Parser, which I have worked with past 2 weeks.
  After my research and having had a look at other's work.
  Present version does only support basic CRUD SQL: INSERT, SELECT, UPDATE, DELETE.
  The first goal is to get it work well with the basic MySQL dialect.
  When this is accomplished, tested and debugged,
  I will add my own Flat File Database as backend.
  My Text File DB uses fwrite() and fread() only. In binary mode: fopen($file, 'wb' ).
  It is also using (different from Ali Faraz's serialized data) DELIMITED strings of data.
  Handled with explode(), implode().

--------------

I have this proposition to you, Scross:
- Let's exchange our codes
- I give you my sql parser script, the version as far as I have come
- You give me your fSQL script
- Let us find a way to discuss and share feedback and thoughts. More exclusive than public forums ...
- Our shared scripts should be strictly confidential.
We do not pass it to anyone else!
Not until you or me feel being ready to release and share in public.

You should know, I am afraid my parser has not settle in final form, yet.
I still have some ideas to make a better program flow structure.
I have chosen to make it one PHP CLASS, where main method is parse($query)
This is the same approach as Ali Faraz have.
But he has broken it down to very small pieces .. char by char,
while I am using more .. word by word .. and doing preg_match() a lot.
--------------

Let me hear what you think
Maybe I could be of some help. I have like 5 years of constant PHP coding experience.
Me having posted >1000 posts at http://phpbuilder.com/board/ to learn, discuss and to help people.


Regards
phpMaster
Sweden 2008-01-20

You can take a look at a demo of my SQL parser in action here: http://ffd.scross.co.uk/fsql/

Just enter a query, run it and it'll basically tell you all the info that the SQL parser spits out. It also tells you when the parser asks for information about a column or supplies information about tables involved in the query. Any errors come up as well. This should give you a better idea of my parser and what it supports thus far.

If you find an error in it (ignoring the fact it might not support a MySql language feature) please tell me, since I'm interested in making it run as smoothly as possible.

Thanks for your quick response.
An online demo, Good!
I have several of those myself, in my PHP working environment.
It spits out a print_r($result) array with the following:
- command (string )
- tablename (string)
- columns (array)
- arguments (array)

I was not really interested of a demo.
I was speaking of coding and sharing php scripts, functions and classes.
And to share, give feedback and ideas to help to go further and make a good parser.

You know 'BRAIN STORMING', don't you?
It is based on the fact that different minds, different experiences and ideas
can contribute an end result that is more than any single mind can think up.
Doesn't matter how clever and smart one person is .. can not accomplish what a group can.
- United we stand, apart we will fall.
- One strand is easily broken. Many strands together will be hard to break!.

I still know as little as before of your interesting works:
- FFD, your flat db
- ICMS, your cms
- FSql, your sql parser

By the way, Scross, did you know that the project name fSQL is already taken!
Is a SQL Parser DB application using flatfile data storage.
I can not say I like the code, at all. It is too much mixed up and without any real structure.
But it works, although with some bugs that should be fixed.

Here you can get it and explore it:

Flat-file SQL(fSQL) is a set of classes available in PHP and Perl
that allows users without SQL databases to store and select their data using SQL queries.
fSQL is designed to support as many SQL queries and features (primarily based on mySQL) as it can.
Flat-file SQL
http://sourceforge.net/projects/fsql/
Latest version released: fSQL v1.2 Released 2006-04-25

Regards
phpMaster

I think I'm going to keep improving the SQL parser, until I feel it has most of the basic SQL functionality, then I'll write some documentation for it and get it released. However, if you want the script now that's fine, just beware that it's a hefty bit of code and with the masses of function calls it can be a bit confusing without proper documentation.

It works like txtSQL 4, in the way that it processes the query character by character, using a tokenizer. The lexer controls the tokenizer and does all the really smart stuff, like converting SQL comparisons and values into PHP code and processing all the different parts of a query. The top level class is just an interface between the lexer and the app using FSQL, and manages communication between FSQL and the app. It also allows the application to specify its own object structured in a custom way, that FSQL will fill with query information.

Anyway, out of interest, if I were to incorporate your code into mine, what benefits do you think it would bring? And I would love to see a demo of your parser so I can give it a try

I did discover that the name fSQL was taken, but I had already developed much of the SQL parser at the time and I decided there was no need to change the name.

Thought I'd would bump this topic as we've had no word for ages.

I guess txtSQL is dead.

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