>
>
> Is the concern that the commit operation of the second transaction will
> itself raise an exception (at which point, the first transaction has
> already been commited)? Aside from that possibility, wouldn't any error
> (within the databases or otherwise) simply result in both transactions
"The greatest disadvantage of the two-phase commit protocol is that it is a
blocking protocol. If the coordinator fails permanently, some cohorts will
never resolve their transactions: After a cohort has sent an *agreement*
message
to the coordinator, it will block until a *commit* or *rollback
On Friday, March 13, 2015 at 7:13:52 AM UTC-4, Niphlod wrote:
>
>
>> Why would you need a commit()? If everything is happening within a web2py
>> request, any open transactions will be rolled back should either database
>> throw an error, or if the app code itself results in an exception. So, if
>
>
> Why would you need a commit()? If everything is happening within a web2py
> request, any open transactions will be rolled back should either database
> throw an error, or if the app code itself results in an exception. So, if a
> record in one database is deleted, but then an exception oc
On Thursday, March 12, 2015 at 5:43:30 PM UTC-4, Niphlod wrote:
>
>
> Within the context of a web2py request, wouldn't there be two transactions
>> open (one for each database)? In that case, at least if the request results
>> in an error, both transactions would be rolled back.
>>
>> Anthony
> Within the context of a web2py request, wouldn't there be two transactions
> open (one for each database)? In that case, at least if the request results
> in an error, both transactions would be rolled back.
>
> Anthony
>
well, pydal isn't used only in web2py's context but even if it was, y
> On Thursday, March 12, 2015 at 4:53:18 PM UTC+1, Anthony wrote:
>>
>> On Thursday, March 12, 2015 at 11:20:15 AM UTC-4, lucas wrote:
>>>
>>> i thought that could be a connection or association that web2py can make
>>> internally but above the database limitations. that should be doable no?
>>
On Thursday, March 12, 2015 at 4:53:18 PM UTC+1, Anthony wrote:
>
> On Thursday, March 12, 2015 at 11:20:15 AM UTC-4, lucas wrote:
>>
>> i thought that could be a connection or association that web2py can make
>> internally but above the database limitations. that should be doable no?
>>
>
> We
On Thursday, March 12, 2015 at 11:20:15 AM UTC-4, lucas wrote:
>
> i thought that could be a connection or association that web2py can make
> internally but above the database limitations. that should be doable no?
>
Well, as Niphlod pointed out, you can still use the IS_IN_DB validator to
main
i thought that could be a connection or association that web2py can make
internally but above the database limitations. that should be doable no?
On Thursday, March 12, 2015 at 11:03:07 AM UTC-4, Anthony wrote:
>
> On Thursday, March 12, 2015 at 10:46:05 AM UTC-4, lucas wrote:
>>
>> yes, would
On Thursday, March 12, 2015 at 10:46:05 AM UTC-4, lucas wrote:
>
> yes, wouldn't DAL need to if it allows for connection(s) to multiple
> databases in the first place?
>
Separate DAL instances can have separate connections to different
databases, but it is an entirely different matter setting up
you can use IS_IN_DB() but that would be an application constraint, not a
db one (which 'reference othertable' creates instead).
On Thursday, March 12, 2015 at 3:46:05 PM UTC+1, lucas wrote:
>
> yes, wouldn't DAL need to if it allows for connection(s) to multiple
> databases in the first place?
yes, wouldn't DAL need to if it allows for connection(s) to multiple
databases in the first place?
lucas
On Thursday, March 12, 2015 at 10:22:32 AM UTC-4, Anthony wrote:
>
> Are you trying to have a table in one database (DAL instance) reference a
> table in a separate database? I don't think t
Are you trying to have a table in one database (DAL instance) reference a
table in a separate database? I don't think the DAL supports that.
Anthony
On Thursday, March 12, 2015 at 10:10:58 AM UTC-4, lucas wrote:
>
> alright, so i have successfully created my new database of states,
> counties,
alright, so i have successfully created my new database of states,
counties, and zip codes. i wanted to recreate it based on a better
database structure so i did it under a new DAL called db_region. however,
when i have a regular db field like in the old, it would have looked like:
Field(
yes, that is working great. the migrate parameter is very good. thanx,
lucas
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message
On the same note,...does anyone know if DAL object can b converted into xml
like the sql designer did? I know web2py no longer probably support sql
designer but if there is a way to convert web2py models into xml then if
someone needs to use mysql or other database or use different framework lik
On the same note,...does anyone know if DAL object can b converted into xml
like the sql designer did? I know web2py no longer probably support sql
designer but if there is a way to convert web2py models into xml then if
someone needs to use mysql or other database or use different framework lik
On the same note,...does anyone know if DAL object can b converted into xml
like the sql designer did? I know web2py no longer probably support sql
designer but if there is a way to convert web2py models into xml then if
someone needs to use mysql or other database or use different framework lik
On the same note,...does anyone know if DAL object can b converted into xml
like the sql designer did? I know web2py no longer probably support sql
designer but if there is a way to convert web2py models into xml then if
someone needs to use mysql or other database or use different framework lik
On the same note,...does anyone know if DAL object can b converted into xml
like the sql designer did? I know web2py no longer probably support sql
designer but if there is a way to convert web2py models into xml then if
someone needs to use mysql or other database or use different framework lik
Also, note that technically, you don't have to move the zip codes to a
third database. You can leave them where they are and just have other apps
access that database (again, making sure only one of the apps is managing
migrations of that table).
Also, depending on the details, you may not need
You can have zipdb = DAL(':
> wouldn't SQL based be better? especially with searching through indexes.
> like i use postgresql and i wouldn't mind sticking with that. lucas
>
> On Thursday, March 5, 2015 at 9:39:21 PM UTC-5, Ron Chatterjee wrote:
>>
>> Once solution I can think of, you can save
wouldn't SQL based be better? especially with searching through indexes.
like i use postgresql and i wouldn't mind sticking with that. lucas
On Thursday, March 5, 2015 at 9:39:21 PM UTC-5, Ron Chatterjee wrote:
>
> Once solution I can think of, you can save them all on a csv file and
> write t
Once solution I can think of, you can save them all on a csv file and write
them on a csv file. import and export on demand and create tables that way.
There are some links I saw about how to create DAL object using csv file.
On Thursday, March 5, 2015 at 8:57:13 PM UTC-5, lucas wrote:
>
> hey
25 matches
Mail list logo
