Jens Rehsack wrote:
Am 11.04.2012 04:58, schrieb Darren Duncan:
That's what I would do if I were making a SQL parser. Oh wait, I am!
Just another SQL Parser? Why not taking/improving one of the
existing ones? Or is it, because they're not invented "here"?
No, not "just another"; I don't do
Am 10.04.2012 17:57, schrieb Tim Bunce:
> On Tue, Apr 10, 2012 at 03:40:12PM +0200, Jens Rehsack wrote:
>>
>> Or - what I like to mention - there's missing a European equivalent for
>> crowd funding.
>>
>> I always wanted to rewrite SQL::Statement reusing ribasushi's great
>> SQL::Translator (allow
Thank you to Jens for expressing his anger by making this public. :)
What a pointless waste on his behalf.
On Tue, Apr 10, 2012 at 1:40 AM, Tim Bunce wrote:
> Hello Jeff.
>
> On Sun, Apr 08, 2012 at 06:43:13AM -0700, Jeff Anderson wrote:
>> Like i said, i was mostly curious of the mindset behi
Am 11.04.2012 04:58, schrieb Darren Duncan:
> Tim Bunce wrote:
>> With regard to migrating SQL::Statement to be built on SQL::Translator,
>> that's clearly a big task, but one that I presume could be broken down
>> into smaller tasks.
>
> I think that it might work better to treat SQL like a gener
Tim Bunce wrote:
With regard to migrating SQL::Statement to be built on SQL::Translator,
that's clearly a big task, but one that I presume could be broken down
into smaller tasks.
I think that it might work better to treat SQL like a general purpose
programming language, as much as is possible
On Tue, Apr 10, 2012 at 03:40:12PM +0200, Jens Rehsack wrote:
>
> Or - what I like to mention - there's missing a European equivalent for
> crowd funding.
>
> I always wanted to rewrite SQL::Statement reusing ribasushi's great
> SQL::Translator (allows to parse different SQL dialects - and have o
Am 10. April 2012 10:40 schrieb Tim Bunce :
> Hello Jeff.
>
> On Sun, Apr 08, 2012 at 06:43:13AM -0700, Jeff Anderson wrote:
>> Like i said, i was mostly curious of the mindset behind this code that go
>> through the hard work of parsing a SQL statement but not providing the
>> ability to alter and
Hello Jeff.
On Sun, Apr 08, 2012 at 06:43:13AM -0700, Jeff Anderson wrote:
> Like i said, i was mostly curious of the mindset behind this code that go
> through the hard work of parsing a SQL statement but not providing the
> ability to alter and reuse that statement.
My answer, for your curiosit
Like i said, i was mostly curious of the mindset behind this code that go
through the hard work of parsing a SQL statement but not providing the
ability to alter and reuse that statement.
You win the pointless code award. Congrats.
On Sun, Apr 8, 2012 at 4:59 AM, Jens Rehsack wrote:
> Am 7. A
So since you would like for me to help improve this module then perhaps you
will allow to explain myself one more time (and CC'ed my personal message
to the group without my permission).
One this here page:
http://search.cpan.org/~rehsack/SQL-Statement-1.33/lib/SQL/Statement/Structure.pod#Executin
Am 7. April 2012 18:01 schrieb Jeff Anderson :
> On Sat, Apr 7, 2012 at 7:10 AM, Jens Rehsack wrote:
>> Am 7. April 2012 11:04 schrieb Jeff Anderson :
>>> On Sat, Apr 7, 2012 at 12:30 AM, Jens Rehsack
>>> wrote:
Am 7. April 2012 01:30 schrieb Jeff Anderson :
> Greetings,
>
> I am
P.S.
> $stmt->from->join[1]->column = 'salary';
should be
$stmt->from->join[1]->table = 'salary';
Sorry about that.
The idea is to have something like what the CGI module provides for HTML.
--
Reinier
I think I do understand, if it's the same thing that I initially
expected when I read that SQL statements are SQL::Statement objects.
SQL::Statement can parse and interpret SQL statements.
It would be useful to expose an object model for parsed statements
allowing the user to read, modify, and cre
Am 7. April 2012 11:04 schrieb Jeff Anderson :
> On Sat, Apr 7, 2012 at 12:30 AM, Jens Rehsack wrote:
>> Am 7. April 2012 01:30 schrieb Jeff Anderson :
>>> Greetings,
>>>
>>> I am wanting to take a SELECT statement and change the names of the
>>> tables without IMMEDIATELY executing that statement
On Sat, 7 Apr 2012 08:30:27 +0100, Jens Rehsack
wrote:
> Am 7. April 2012 01:30 schrieb Jeff Anderson :
> > Greetings,
> >
> > I am wanting to take a SELECT statement and change the names of the
> > tables without IMMEDIATELY executing that statement. I was hoping that
> > SQL::Statement would so
Am 7. April 2012 01:30 schrieb Jeff Anderson :
> Greetings,
>
> I am wanting to take a SELECT statement and change the names of the
> tables without IMMEDIATELY executing that statement. I was hoping that
> SQL::Statement would solve the problem but apparently it can only
> EXECUTE a statement. Is
16 matches
Mail list logo
