Multi Database + Huge lookups

[alexan...@gmail.com]

Hi

I've a big project implemented in Delphi/C++/MSSQL that I want to migrate to the WEB and Python/Django is my choice.

But I'm getting some dificulties probably due to the backgroud I came from.

1-

I've have several databases One of them is for static tables like zipcodes Districts countrys, and a lot more stuff they rarely change, the others are one per enterprise/domain, taht all share common data on the statis one.

Is this solution implementable under django?

2- 

I've huge tables like ZIP codes milions or records how to do a foreign key that is not in a select but in an autocomplete. (is this django builtin)?

3-

Several times I've lookups where I copy more info than the key, for exemple in an invoice I copy the ClientID, but also the adress do the invoice, so if the adress changes in a future the invoice is imutable...

I would appreciate help to Kickstart me

Regards

Alexandre Rua

[Russell Keith-Magee]

On Mon, Nov 19, 2012 at 10:06 PM, alexan...@gmail.com <alexan...@gmail.com> wrote:

Hi

I've a big project implemented in Delphi/C++/MSSQL that I want to migrate to the WEB and Python/Django is my choice.

But I'm getting some dificulties probably due to the backgroud I came from.

1-

I've have several databases One of them is for static tables like zipcodes Districts countrys, and a lot more stuff they rarely change, the others are one per enterprise/domain, taht all share common data on the statis one.

Is this solution implementable under django?

Yes. See https://docs.djangoproject.com/en/1.4/topics/db/multi-db/

 

2- 

I've huge tables like ZIP codes milions or records how to do a foreign key that is not in a select but in an autocomplete. (is this django builtin)?

Builtin - no; but that's part of the design philosophy of Django. Django is a server side framework, and as such, it doesn't make any decisions about the front end. However, it's trivial to use something like JQueryUI to put an autocomplete widget on your site, and have it backed by an AJAX request served by your Django server.

There are also a number of projects (e.g., dajax) that provide even easier wrappers.

 

3-

Several times I've lookups where I copy more info than the key, for exemple in an invoice I copy the ClientID, but also the adress do the invoice, so if the adress changes in a future the invoice is imutable...

I'm not sure I understand the question here. However, Django provides a convenient wrapper around database queries, so if you can do what you want on a database, there should be a way to expose that query into Django.

Yours,

Russ Magee %-)

[alexan...@gmail.com]

Thanks

I will follow directions