The FB reflection code does not raise the appropriate error when the
table does not exist. This is checked by a test, that clearly fails.
The attached patch cures the problem.
ciao, lele.
Fri Oct 6 23:09:17 CEST 2006 [EMAIL PROTECTED]
* Firebird reflection wasn't raising the proper NoSuchTa
Michael Bayer wrote:
any dropping of "AS" for alisases has to occur locally within the
firebird dialect;
That's of course what I meant.
feel free to send a patch. I have no test instance of firebird here
I'm attaching two patches, one that enables the test frameword for
firebird, and one
Ezio Vernacotola wrote:
> A possible workaround is switch to firebird 2.0 now, is very close to
> final release, largely backward compatible and accepts "AS" in table
> aliasing
Unfortunately it's not an easy switch, so I gently insist SA should drop
the "AS" keyword usage, even from the column
Ezio Vernacotola wrote:
> I don't understand what you are trying do to with column and table aliasing.
> Can you give some code example to better explain your problem?
>
I think it is not relevant: effectively Firebird does not like the table
alias introduced by "AS", so most probably the FB bac
Uwe Grauer wrote:
> i saw another issue with func.now().
> But i do not know how to deal with it.
> In FB you can't use something like 'select now from rdb$database'.
> I think the usage of such things is database specific.
The FB idiom for that is either
SELECT cast('now' as timestamp) FROM r
Jonathan Ellis wrote:
> I don't think that would be better at all. It implies that x, y, and z
> are all optional parameters, which usually isn't the case.
Well, that's up to the developer of the SP, isn't it? I mean, the SP
could react appropriately when one or more of its parameters is NULL.
Arnar Birgisson wrote:
> On 6/13/06, Lele Gaifax <[EMAIL PROTECTED]> wrote:
>> As said above, I'd use a different name for it,
>> though, as I find "Function" a bit misleading. Isn't ParametricTable a
>> better choice?
>
> Or perhaps &quo
Michael Bayer wrote:
>
> On Jun 13, 2006, at 4:03 AM, Lele Gaifax wrote:
>
>>
>> Wouldn't something like
>>
>>diary = FunctTable('diary(:iddip,:fromdate,:todate,:live)', ...)
>>
>> be a viable solution to the problem as we
Michael Bayer wrote:
> ideally you should be able to say:
>
> func.diary(iddip, fromd, tod, True).select()
>
> however this will produce "SELECT diary(?, ?, ?, ?)" which isnt going to
> work since its naming the function as a column. Function objects in SA
> currently are designed to follo
Hi,
I'm having some trouble figuring out the best way to fetch data from a
selectable stored procedure on a PG database.
The only solution I found is the following::
results = metadata.engine.text(
'select iddip, day, amount '
'from diary(:iddip,:fromdate,:todate,:live)'
).exe
10 matches
Mail list logo
