Well, ideal for me would be to define a prefix in the model file and this 
is automatically added to every defined table and all queries (no idea if 
it is possible).

But this multi-tenancy looks interesting as well, so I will look into it...

Thanks!

Regards, Chris


On Monday, November 26, 2012 4:17:57 PM UTC+1, Anthony wrote:
>
> Do you have a proposal for how an easier implementation should work?
>
> Also, rather than separate tables for different clients, have you 
> considered either 
> multi-tenancy<http://web2py.com/books/default/chapter/29/06#Common-fields-and-multi-tenancy>or
>  just using separate databases (in the latter case, you could just define 
> the DAL connection string dynamically to refer to the appropriate database)?
>
> Anthony
>
> On Monday, November 26, 2012 10:09:18 AM UTC-5, Chr_M wrote:
>>
>> I guess that nobody has ever had a need for this and that there is not 
>> really a solution for it?
>>
>> Regards, Chris
>>
>>
>> On Friday, November 23, 2012 9:09:24 PM UTC+1, Chr_M wrote:
>>>
>>> That, but even the same app using different tables in the same db (but 
>>> for different cliënts)...
>>>
>>> Regards, Chris
>>>
>>>
>>> On Friday, November 23, 2012 7:00:28 PM UTC+1, Richard wrote:
>>>>
>>>> Why exactly you change prefix? Installing differents apps dbs in the 
>>>> same db?
>>>>
>>>> Richard
>>>>
>>>> On Fri, Nov 23, 2012 at 10:57 AM, Chr_M <chr....@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am new to web2py and am migrating an application to web2py. All the 
>>>>> tables have a prefix that changes for the different deployments of the 
>>>>> application. Is there a way in web2py to have a prefix for all the tables 
>>>>> in the database that I can change easely for different deployments?
>>>>>
>>>>> At this time I use a 
>>>>>
>>>>> PREFIX = 'prefix_' 
>>>>>
>>>>> constant and define tables with 
>>>>>
>>>>> db.define_table(PREFIX + 'table_name', etc...
>>>>>
>>>>> but this is becoming a bit complicated when defining requirements etc. 
>>>>> Maybe there is an easier solution?
>>>>>
>>>>> Thanks in advance.
>>>>>
>>>>> Regards, Chris
>>>>>
>>>>>  -- 
>>>>>  
>>>>>  
>>>>>  
>>>>>
>>>>
>>>>

-- 



Reply via email to