prove the annuoncement with a small recap of what
Firebird is and when one might use it ;)
—Adam
On Sat, 24 Aug 2024, at 12:11, mariuz wrote:
> New pull request merged into Firebird Django driver with the following
> changes :
>
> Added support for Django 5.0
> Added support for
New pull request merged into Firebird Django driver with the following
changes :
Added support for Django 5.0
Added support for partial indexes
Added support for window functions
Added support for TIME WITH TIME ZONE and TIMESTAMP WITH TIME ZONE for
TimeField and DateTimeField
Added support for
>>>
>>> A few years ago something similar was causing issues with the Oracle
>>> backend. To resolve it, Mariusz added a clevar hack, relying on named
>>> parameters -- he made sure that if the same parameter value is used
>>> more than once, t
r hack, relying on named
>> parameters -- he made sure that if the same parameter value is used
>> more than once, then the statement re-uses the parameter name, passing
>> the value only once. So, in your case, the equivalent would be
>> something like
>>
>&g
relying on named
> parameters -- he made sure that if the same parameter value is used
> more than once, then the statement re-uses the parameter name, passing
> the value only once. So, in your case, the equivalent would be
> something like
>
> ...
> "EXPRESSIONS_COM
CONTACT_ID", %arg1 AS "FOO" FROM
"EXPRESSIONS_COMPANY" WHERE %arg1 = %arg1 ORDER BY
"EXPRESSIONS_COMPANY"."NAME" ASC'
with
cursor.execute(sql, [], arg1='value')
This was relatively easy to do in the Oracle backend, which has always
used
here some reason you think there's an issue with the SQL being
> constructed?
>
No, I don't think that the sql statement is wrong. I just traying to
figured out how the sql is generated by Django and why it fails in Firebird.
I found the answere, of course, there is a Firebir
It looks correct to me. RawSQL is defining a parameter to be included in
the query. The RawSQL expression itself is used in the select and on the
left hand side of the WHERE clause, so the parameter needs to be included
there. The right hand side of the WHERE clause is a regular string (which
j
Hi,
Testing expressions test app, the query generated into
BasicExpressionsTests.test_annotate_values_filter method:
companies = Company.objects.annotate(
foo=RawSQL('%s', ['value']),
).filter(foo='value').order_by('name')
Generate:
'SELECT "EXPRESSIONS_COMPANY"."ID", "EXPRESSIONS_COMPANY"."N
Hi folks,
I'm here again trying to up to date the django-firebird backend.
The last stable version was for django 1.8 LTS, that came to end of life,
so I want to update to 1.11 LTS first and then to 2.0.
Having said that, one of unresolved things is about adding a non-nullable
field
hi. i will make some testes with firebird 2.0.5 and access to comercial
software lojafacil that use firebird. thanks for message.
2016-04-06 8:13 GMT-03:00 mariuz :
> The current master branch is being developed under django 1.8.x
>
> This is still in alpha status but I think the base c
The current master branch is being developed under django 1.8.x
This is still in alpha status but I think the base code works pretty well.
Any feedback wiil be appreciated.
https://github.com/maxirobaina/django-firebird/commits/master
--
You received this message because you are subscribed
t;
>>>>> Maxi, did you want to submit a patch, or do you want me to add it at
>>>>> some point next week!
>>>>>
>>>>> Andrew
>>>>>
>>>>
>>>> I'll appreciate if you can add it.
>>>> BT
bmit a patch, or do you want me to add it at
>>>> some point next week!
>>>>
>>>> Andrew
>>>>
>>>
>>> I'll appreciate if you can add it.
>>> BTW, are there other areas that need some work, for instance, add_field
do you want me to add it at
>>> some point next week!
>>>
>>> Andrew
>>>
>>
>> I'll appreciate if you can add it.
>> BTW, are there other areas that need some work, for instance, add_field
>> method [1], if I try to delete a default valu
want to submit a patch, or do you want me to add it at some
>> point next week!
>>
>> Andrew
>>
>
> I'll appreciate if you can add it.
> BTW, are there other areas that need some work, for instance, add_field
> method [1], if I try to delete a default value
t.
BTW, are there other areas that need some work, for instance, add_field
method [1], if I try to delete a default value on a column that does not
have a previous default value definition I get an error on firebird, for
which reason, I need to check if that field has got defined a default val
_null_suffix =
>>> "" or similar - do you think that would be a reasonable approach?
>>>
>>> Andrew
>>>
>>>
>>> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm tryi
reasonable approach?
>
> Andrew
>
>
> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
> Hi,
>
> I'm trying to implement the new schema migration of django 1.7 for
> django-firebird backend.
> In column_sql method, when the field can be null, in firebird,
imilar - do you think that would be a reasonable approach?
>>
>> Andrew
>>
>>
>> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
>>
>>> Hi,
>>>
>>> I'm trying to implement the new schema migration of django 1.7 for
>>> django-f
ed
> on the schema editor class itself, and then you could set sql_null_suffix =
> "" or similar - do you think that would be a reasonable approach?
>
> Andrew
>
>
> On Wed, May 14, 2014 at 7:05 AM, maxi wrote:
>
>> Hi,
>>
>> I'm trying to implemen
ay 14, 2014 at 7:05 AM, maxi wrote:
> Hi,
>
> I'm trying to implement the new schema migration of django 1.7 for
> django-firebird backend.
> In column_sql method, when the field can be null, in firebird, is not
> necessary add the NULL keyword. So to change this behavior I n
Hi,
I'm trying to implement the new schema migration of django 1.7 for
django-firebird backend.
In column_sql method, when the field can be null, in firebird, is not
necessary add the NULL keyword. So to change this behavior I need override
the entire column_sql method just to change one
El miércoles, 12 de febrero de 2014 15:11:33 UTC-3, Florian Apolloner
escribió:
>
> Nice, can you also upload wheel packages?
>
Done!
For now, just for the stable version (django-firebird with django 1.5
support)
>
> On Wednesday, February 12, 2014 2:19:11 PM UTC+1, mariuz wr
Nice, can you also upload wheel packages?
On Wednesday, February 12, 2014 2:19:11 PM UTC+1, mariuz wrote:
>
> Here are a few fixes for v1.6.x Release Candidate 1 commited into
> master<https://github.com/maxirobaina/django-firebird>
> ——
Here are a few fixes for v1.6.x Release Candidate 1 commited into
master<https://github.com/maxirobaina/django-firebird>
Fixed missing date_interval_sql implementation. #21
Fixed datetime_trunc_sql NotImplementedError. #20
Fixed m
On 2-8-2012 14:40, Anssi Kääriäinen wrote:
> It seems there is need for "max decimal digits" feature or something
> like that
Actually, what I'm interested in is that anything from a model field
definition that can apply to a form field (yes, that general) is added
to a form field's attributes of
It seems there is need for "max decimal digits" feature or something
like that, so that one can skip the failing tests... Please file a
ticket.
- Anssi
On 2 elo, 09:29, mariuz wrote:
> We need your opinions , patches ideas
>
> https://groups.google.com/forum/?fromgroups#!to
We need your opinions , patches ideas
https://groups.google.com/forum/?fromgroups#!topic/django-firebird-dev/SUXh2Jpwgnc
ps: yes we moved to github
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion
Hi,
I've opened a ticket for months ago -
http://code.djangoproject.com/ticket/13159.
Only needs a test case.
David Elias
On Jul 23, 10:30 pm, maxi wrote:
> Hi,
>
> I'm working on django-firebird project and doing some modifications
> for work with django 1.2
>
On 23 jul, 18:58, Alex Gaynor wrote:
> On Fri, Jul 23, 2010 at 4:56 PM, maxi wrote:
>
> > On 23 jul, 18:42, Alex Gaynor wrote:
> >> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote:
> >> > Hi,
>
> >> > I'm working on django-firebird project and
On Fri, Jul 23, 2010 at 4:56 PM, maxi wrote:
>
>
> On 23 jul, 18:42, Alex Gaynor wrote:
>> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote:
>> > Hi,
>>
>> > I'm working on django-firebird project and doing some modifications
>> > for work wi
On 23 jul, 18:42, Alex Gaynor wrote:
> On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote:
> > Hi,
>
> > I'm working on django-firebird project and doing some modifications
> > for work with django 1.2
> > Right now, I'm trying to pass some tests running the t
On Fri, Jul 23, 2010 at 4:30 PM, maxi wrote:
> Hi,
>
> I'm working on django-firebird project and doing some modifications
> for work with django 1.2
> Right now, I'm trying to pass some tests running the tests suit of
> django trunk code and I found the next prob
Hi,
I'm working on django-firebird project and doing some modifications
for work with django 1.2
Right now, I'm trying to pass some tests running the tests suit of
django trunk code and I found the next problem:
django is trying to execute this sql:
SELECT "AGGREGATION_BOOK&
Hello everyone, I want to make a summary of the changes implemented in
recent times about the project django-firebird:
http://code.google.com/p/django-firebird/
http://tech.groups.yahoo.com/group/firebird-python/message/254
--
You received this message because you are subscribed to the Google
Maxi,
I do have a few bugfixes for the firebird-backend. How can we get in
touch?
Regards,
Thomas
On Sep 28, 11:26 pm, maxi wrote:
> Hi,
> I'm working on implementation of firebird backend for django [1]
> I've an issue related of icontains filter option. Firebird us
On Mon, Sep 28, 2009 at 6:26 PM, maxi wrote:
>
> Hi,
> I'm working on implementation of firebird backend for django [1]
> I've an issue related of icontains filter option. Firebird uses
> CONTAINING sql clause for this, which is case insesitive.
>
> The probl
Hi,
I'm working on implementation of firebird backend for django [1]
I've an issue related of icontains filter option. Firebird uses
CONTAINING sql clause for this, which is case insesitive.
The problem is that the output generated (where clause) is wrong.
It return:
WH
On Jun 12, 10:26 am, mariuz wrote:
> Seems that we have a new firebird django maintainer
>
> http://www.firebirdnews.org/?p=2964
>
> I will check the new work on weekend and do some small tests
here is source code now up in svn
http://code.google.com/p/
Seems that we have a new firebird django maintainer
http://www.firebirdnews.org/?p=2964
I will check the new work on weekend and do some small tests
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
On Mar 19, 8:58 am, stout.el...@gmail.com wrote:
> Hi, I've got it working a couple months ago, just with basic
> funcionality, without the features Ivan put it
> inhttp://code.google.com/p/django-firebird/.
>
> It's not finished or clean, but if you want i can send
Hi, I've got it working a couple months ago, just with basic
funcionality, without the features Ivan put it in
http://code.google.com/p/django-firebird/.
It's not finished or clean, but if you want i can send you later.
Regards,
David Elias
On Mar 18, 4:07 pm, mariuz wrote:
> On
On Mar 16, 4:34 pm, mariuz wrote:
> any progress with firebird driver ? I see an old post from 2008 if i
> search the archives for firebird+database
> Maybe I should try to create the tutorial db and add the patches
>
> I want to show some demo to the python meetup in boston if
any progress with firebird driver ? I see an old post from 2008 if i
search the archives for firebird+database
Maybe I should try to create the tutorial db and add the patches
I want to show some demo to the python meetup in boston if it will
work :)
http://python.meetup.com/181/calendar
On Mon, Jan 19, 2009 at 3:33 PM, Harryanto Ie wrote:
> can you help me?
> 1. what kind of database can be associate with django?
> 2. is there any possiblity if we use django applicated
> with firebird databases? how?
1. Django-developers is for discussing the development of Django
can you help me?
1. what kind of database can be associate with django?
2. is there any possiblity if we use django applicated
with firebird databases? how?
thx
"
I am trying to download the trunk from SVN and am getting this message
Error: MKACTIVITY of '/svn/!svn/act/b31d46c1-39f8-164f-
a712-4e3a3dd6a803': 400 Bad Request (http://code.djangoproject.com)
On May 5, 6:19 pm, Ivan Illarionov <[EMAIL PROTECTED]> wrote:
> Hi, Rahein,
>
r all your help everyone.
On Mon, May 5, 2008 at 6:19 PM, Ivan Illarionov <[EMAIL PROTECTED]>
wrote:
>
> Hi, Rahein,
>
> The Firebird patch and backend is against latest Django trunk and
> depends on the newest Django features, especially new QuerySet/Query
> classes. Ple
Hi, Rahein,
The Firebird patch and backend is against latest Django trunk and
depends on the newest Django features, especially new QuerySet/Query
classes. Please note that there are known bugs with very complex ORM
queries. It's also important to use the latest Firebird (> 2.0).
Ahh that must be it, thanks. I am using 0.96.1. I am about to head out for
the day, but I will try it with the current trunk tomorrow.
Thanks for your help Ian.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
or.execute("SELECT 1 FROM %s WHERE %s=%%s ROWS 1" % \
>
>
> Shouldn't that FB patch have fixed this type of stuff? Did I apply it
> wrong?
It sounds like you're using an old version of Django. That line was
fixed nearly a year ago when the Oracle branch was merg
wrote:
> >> The real problem is when I try to access the database. I get
> >> stack trace below. It looks like it is trying to use the
> >> LIMIT keyword incorrectly.
>
> As best I can tell, Firebird doesn't support the SELECT ... LIMIT
> x OFFSET y&quo
I am really learning the internals of Django.
I changed line 208 in db\models\base.py from:
cursor.execute("SELECT 1 FROM %s WHERE %s=%%s LIMIT 1" % \
to:
cursor.execute("SELECT 1 FROM %s WHERE %s=%%s ROWS 1" % \
Shouldn't that FB patch have fixed this type of stuff? Did I apply it
wrong?
--
>> The real problem is when I try to access the database. I get
>> stack trace below. It looks like it is trying to use the
>> LIMIT keyword incorrectly.
As best I can tell, Firebird doesn't support the SELECT ... LIMIT
x OFFSET y" notation, but rather uses &quo
Well I changed \backends\firebird\base.py to print out the SQL
statement, it is:
SELECT 1 FROM "BOOKS_PUBLISHER" WHERE "ID"=%s LIMIT 1
Instead of LIMIT it should says ROWS. Any idea how to fix this?
--~--~-~--~~~---~--~~
You received this
I am trying to get Django working with Firebird as the database
backend. I have done some searching and found kinterbasdb and the
firebird patch to get it to work with Django.
I am trying to follow the free books tutorial, but having problems.
First the creation of the tables in the DB didn
t's not really going to be a backend that existing
> Firebird users can use if that were the minimum.
>
> I realise that last sentence doesn't help at all with solving your
> problem. Merely pointing out the PR problem this presents.
Yes you're right. The iendswith on TextF
;
> These work well with VARCHAR using LIKE and the UPPER function just
> like the oracle branch, but only in Firebird 2.1 it's possible to
> treat a BLOB with 32k limit size like a VARCHAR.
>
> For __icontains firebird has CONTAINING but that does not use index.
> Some
cle branch, but only in Firebird 2.1 it's possible to
treat a BLOB with 32k limit size like a VARCHAR.
For __icontains firebird has CONTAINING but that does not use index.
Some special case could be used if we knew the field type in
"query.get_where_clause" function, maybe with the r
I've uploaded a new patch against the oracle branch and updated the
backend module.
You can check http://code.djangoproject.com/ticket/1261
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
Is there anything i can help with? I m don´t have much python knowledge
Same with me :)
but i m really interested in firebird support in django, so
if i can help testing or doing something it will be a pleasure.
Well you can use this patch on your projects and report bugs and
enhancements
Thanx again, it worked perfectly now.
Is there anything i can help with? I m don´t have much python
knowledge but i m really interested in firebird support in django, so
if i can help testing or doing something it will be a pleasure.
also, is there any plans to add it in the main django
I was able to reproduce this error by enable the admin in the
INSTALLED_APPS and in urls.py but not sync'ed to database, make sure
you call manage.py syncdb to install also the admin app.
Fabio Gomes escreveu:
Thanx, it worked now.
I was able to create the table, acess the objects, add, update
n 530.')
On 12/18/06, David Elias <[EMAIL PROTECTED]> wrote:
Make sure you are using the boulder-oracle-sprint branch and your
PYTHONPATH is pointing to that.
Fabio Gomes wrote:
> I tried it and i m getting this error:
>
>
> File "/usr/lib/python2.4/site-packages/dj
Make sure you are using the boulder-oracle-sprint branch and your
PYTHONPATH is pointing to that.
Fabio Gomes wrote:
> I tried it and i m getting this error:
>
>
> File "/usr/lib/python2.4/site-packages/django/db/backends/firebird/base.py",
> line 100, in quo
I tried it and i m getting this error:
File "/usr/lib/python2.4/site-packages/django/db/backends/firebird/base.py",
line 100, in quote_name
name = '"%s"' % util.truncate_name(name.upper(), get_max_name_length())
AttributeError: 'module' object has
Thanx man, i ll test it right away.
I was trying to hack your old one, but i didnt figure out why some
generators weren´t created, so i was having some problems.
-- Forwarded message --
From: David Elias <[EMAIL PROTECTED]>
Date: Dec 18, 2006 1:14 PM
Subject: New fi
Please check http://code.djangoproject.com/ticket/1261
David Elias
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
On 6/6/06, David Elias <[EMAIL PROTECTED]> wrote:
> Adrian, assuming that you are working on database support, are any
> plans that each backend may add sql statements to the sqlall output in
> the future?
I've got nothing against adding a backend-specific hook for altering
the "sqlall" output. W
Already added the patch, for the ones that didn't know -
http://code.djangoproject.com/ticket/1261
I'm trying to remove the "if settings.DATABASE_ENGINE == 'firebird'"
from management.py and add some signals to use with the dispatcher.
Already got this working insid
On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote:
> I've got the backend's base, create and introspection almost done.
> Should i create a ticket or use this one
> http://code.djangoproject.com/ticket/1261 and attach the files?
Go ahead and use that existing ticket. Looking forward to your patch!
I've got the backend's base, create and introspection almost done.
Should i create a ticket or use this one
http://code.djangoproject.com/ticket/1261 and attach the files?
David
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
time.
> What do you have coded so far?
>
> Adrian
>
> --
> Adrian Holovaty
> holovaty.com | djangoproject.com
Hi,
I have made some nasty changes in management.py for quick testing,
removed "referencing" when creating contraints, but that will not
resolve the column name siz
Michael Radziej wrote:
> David Elias wrote:
> > Well, AS in FROM clause is not support...
>
> Not even in the equivalent form
>
> SELECT ... FROM table_name alias
>
> ?
>
> That would really suck. How do you do joins to "self" then?
>
> Michael
With all the work i've forgot that, made a simple t
On 6/1/06, David Elias <[EMAIL PROTECTED]> wrote:
>
> Well, AS in FROM clause is not support...
>
> Thoughts, ideas...?
Hey David,
Sorry for the slow response -- let's take each issue one at a time.
What do you have coded so far?
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~
David Elias wrote:
> Well, AS in FROM clause is not support...
Not even in the equivalent form
SELECT ... FROM table_name alias
?
That would really suck. How do you do joins to "self" then?
Michael
--~--~-~--~~~---~--~~
You received this message because you a
Well, AS in FROM clause is not support...
Thoughts, ideas...?
I think we're not going to have Firebird support in Django :p
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gr
d could overwrite or
not.
Another thing is if it could be created something like
"pre_create_table" and "post_create_table" with the dispatcher
framework to create triggers, sequences, domains etc, thoughts?
I'm a python and firebird newbie so i could missing something ..
> Hi David,
Hi, thanks for the response.
> I don't know of any work being done on a Firebird adapter. Would you
> like to volunteer? :)
Shure :) at work we are building a portal that will work as bridge
between the our software (similar to SAP) and it uses Firebird, so it's
On 4/28/06, David Elias <[EMAIL PROTECTED]> wrote:
> Is anyone working on this?
>
> I already found some problems for the firebird adapter, or not :)
>
> For example the LIMIT OFFSET clause, firebird uses SELECT FIRST SKIP
> and the sql construction in django implies
Hi there,
Is anyone working on this?
I already found some problems for the firebird adapter, or not :)
For example the LIMIT OFFSET clause, firebird uses SELECT FIRST SKIP
and the sql construction in django implies that the limit offset is
always appended with the backed.get_limit_offset_sql
On 10/17/05, BleSS <[EMAIL PROTECTED]> wrote:
> Anybody is going to write the firebird db backend?
I don't have Firebird installed yet, but if you'd like to kickstart
the DB backend, it'd be really easy to do. Just create "firebird.py"
in django/core/db/backends
Anybody is going to write the firebird db backend, or is working on it?
Anybody is going to write the firebird db backend?
85 matches
Mail list logo