senthadev

pipeSQL author here:

Sorry, I didn't understand your answer. It is very important to understand the complex query in-order to debug or re-engineer. One way is to visualise it as mentioned in the article and convert it to SQL via pipeSQL.

You should try to implement the Fib with tail call and then test it. http://en.wikipedia.org/wiki/Tail_call

Piping is used to merge the tables rows. Tables can be merged in multiple ways, for example by join, left join, exists, not exists, union, minus etc.. And you can have the pipe chain up to 255 levels.

This is an example where SQL can be written in multiple ways to get the same result. It doesn't matter how many lines SQL contains since its all depends on how the database engine going to execute it. Therefore, pipeSQL's main aim is to make it easier to read and understand the query after couple of days/weeks :) .

This is not a replacement for SQL. Its a tool to create SQL in a different angle. An angle which is similar to UNIX pipeline concept.

API would be charge by usage. But the desktop APP will be one time payment(per year) since it will include the parser to translate the pipeSQL to database dialect. Still not finalised, but happy to hear your thoughts on the pricing model.

Main aim of this tool is to create complex queries in a bottom-up approach. Say you want to create a query by joining 5 tables. Even though we declare 5 tables in the FROM clause, database will join 2 at a time. And then join another table with the previous result set. So this tool helps to build query similar to execution plan tree structure.

This is a tool to generate complex queries in a bottom-up approach. Once the SQL is generated, then we can use the SQL in the application for future use. It's not another layer between apps and database.

Exactly, its a tool to generate SQL in a elegant manner. Once the SQL is generated, we can uses the generated SQL in the app. There is no need of a new additional layer between apps and database.

How about sending binary SMS such as SIM-RFM messages?

Thanks for aggregating and publishing the links.

Functional programming using F#

Traveling in the same boat as you do, not eligible to advice. Although I read in HN before that burnt out is a signal by the brain stating that we are working without any foreseeable reward.

Hello nabo :), definitely we should have some beer. My contact email is in profile.

Bank sector and USSD are good combination, but banking sector doesn't interest me. Thanks for the input.

Yes, this looks interesting. thanks.

SEEKING TO SOLVE MOBILE COMMUNICATION PROBLEMS:

I have built my knowledge around (U)SIM (SmartCard) and SMS (deeper level such as binary SMS etc.). Please do contact me : senthadev'at'gmail.com

Vinod khosla (Sun co-founder) says "Fail Fast", meaning that learn all the possibilities (specially the dead ends, how not to use) of the new technology/idea before competitors do. So when the competitors place their baby step on the idea you're more far from the starting line. Good luck.

This is what I was looking for, data producers control their own data and manage the app providers to use the data..

Self hosting real time "Commenting" web application with text mining/taming functionality. (A replacement for Disque)

I agree.

totally agree.

please don't misuse this site..

No, its only a normal employee contract.

Yes, this is what I was thinking. thanks.

Its a product which is build based on open standard (3gpp specifications). So I could develop it, even if I have signed any agreements with them, right ?

"Do more faster" by David cohen and Brad feld. A must have book.

In a public toilet, a cleaner is mopping the floor. And a new start-up owner enters in: Start-up owner (in his mind):poor guy, has to do this worse job to earn money. Cleaner (in his mind):I'm so happy that my job is helping people to have a good health buy keeping this toilet clean.

Same job, different perspective.

Facebook is down in oslo, 500 internal server error.

I did browse the beanstalkd, but I didn’t try it. Since we were moving our infrastructure to aws, it was feasible for us to use aws simple queue service. And I’m using long polling (which will wait 20 seconds to reconnect again) and bulk sending to reduce the no of calls to SQS.