Motion: vote MapGuide RFC 78

[Tom Fukushima]

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?  Does the user need to rollback transaction within exception handling, or is this done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in the exception handler.

In case that FDO provider doesn't support transaction, it throws exception?
>>> RFC updated: if a provider doesn't support transaction, BeginTransaction() will throw an MgInvalidOperationException saying transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another question comes to me. I assume that MgTransaction will get hold on one particular FDO connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until Commit or Rollback is executed. And there is also a timeout for transaction that if it's not committed or rollbacked within the timeout, the server will automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Trevor Wekel]

Do we also want to clarify which providers support transactions in the Doxygen generated documentation?  It might save some traffic on the mapguide-users list.

+1 Trevor


-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Tom Fukushima
Sent: Monday, July 27, 2009 9:55 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 78

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?  Does the user need to rollback transaction within exception handling, or is this done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in the exception handler.

In case that FDO provider doesn't support transaction, it throws exception?
>>> RFC updated: if a provider doesn't support transaction, BeginTransaction() will throw an MgInvalidOperationException saying transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another question comes to me. I assume that MgTransaction will get hold on one particular FDO connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until Commit or Rollback is executed. And there is also a timeout for transaction that if it's not committed or rollbacked within the timeout, the server will automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Andy Morsell]

+1 Andy



-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
Sent: Monday, July 27, 2009 8:55 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 78

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?  Does
the user need to rollback transaction within exception handling, or is this
done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in the
exception handler.

In case that FDO provider doesn't support transaction, it throws exception?
>>> RFC updated: if a provider doesn't support transaction,
BeginTransaction() will throw an MgInvalidOperationException saying
transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another question
comes to me. I assume that MgTransaction will get hold on one particular FDO
connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until
Commit or Rollback is executed. And there is also a timeout for transaction
that if it's not committed or rollbacked within the timeout, the server will
automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom



_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Paul Spencer-2]

+1 Paul

On 27-Jul-09, at 1:37 PM, Andy Morsell wrote:

> +1 Andy
>
>
>
> -----Original Message-----
> From: Tom Fukushima [mailto:[hidden email]]
> Sent: Monday, July 27, 2009 8:55 AM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] Motion: vote MapGuide RFC 78
>
> Hi,
>
> I motion for a vote on
>
> MapGuide RFC 78 - Enhance transaction capability to Feature Service
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78
>
> Summary of review:
>
> What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery  
> fails?  Does
> the user need to rollback transaction within exception handling, or  
> is this
> done automatically?
>>>> No action taken.  To give flexibility, the user can do a Rollback  
>>>> in the
> exception handler.
>
> In case that FDO provider doesn't support transaction, it throws  
> exception?
>>>> RFC updated: if a provider doesn't support transaction,
> BeginTransaction() will throw an MgInvalidOperationException saying
> transaction is not supported.
>
> I think too that it doesn't have to do auto roll back but another  
> question
> comes to me. I assume that MgTransaction will get hold on one  
> particular FDO
> connection until either Rollback or Commit is executed ?
>>>> Yes, MgTransaction will hold on the particular FDO connection until
> Commit or Rollback is executed. And there is also a timeout for  
> transaction
> that if it's not committed or rollbacked within the timeout, the  
> server will
> automatically rollback the transaction as mentioned in the RFC.
>
> Add a UpdateFeatures that uses transaction:
>>>> Description added.
>
> +1 Tom
>
> Thanks
> Tom
>
>
>
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals

__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Haris Kurtagic]

+1 Haris

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Andy
Morsell
Sent: Monday, July 27, 2009 7:37 PM
To: 'MapGuide Internals Mail List'
Subject: RE: [mapguide-internals] Motion: vote MapGuide RFC 78

+1 Andy



-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
Sent: Monday, July 27, 2009 8:55 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 78

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?
Does
the user need to rollback transaction within exception handling, or is
this
done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in
the
exception handler.

In case that FDO provider doesn't support transaction, it throws
exception?
>>> RFC updated: if a provider doesn't support transaction,
BeginTransaction() will throw an MgInvalidOperationException saying
transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another
question
comes to me. I assume that MgTransaction will get hold on one particular
FDO
connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until
Commit or Rollback is executed. And there is also a timeout for
transaction
that if it's not committed or rollbacked within the timeout, the server
will
automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom



_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Jason Birch]

+1 Jason

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Haris Kurtagic
Sent: Monday, July 27, 2009 12:00 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Motion: vote MapGuide RFC 78

+1 Haris

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Andy
Morsell
Sent: Monday, July 27, 2009 7:37 PM
To: 'MapGuide Internals Mail List'
Subject: RE: [mapguide-internals] Motion: vote MapGuide RFC 78

+1 Andy



-----Original Message-----
From: Tom Fukushima [mailto:[hidden email]]
Sent: Monday, July 27, 2009 8:55 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 78

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?
Does
the user need to rollback transaction within exception handling, or is
this
done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in
the
exception handler.

In case that FDO provider doesn't support transaction, it throws
exception?
>>> RFC updated: if a provider doesn't support transaction,
BeginTransaction() will throw an MgInvalidOperationException saying
transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another
question
comes to me. I assume that MgTransaction will get hold on one particular
FDO
connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until
Commit or Rollback is executed. And there is also a timeout for
transaction
that if it's not committed or rollbacked within the timeout, the server
will
automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom



_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Kenneth Skovhede, GEOGRAF A/S]

+1 Kenneth

Regards, Kenneth Skovhede, GEOGRAF A/S



Tom Fukushima skrev:

> Hi,
>
> I motion for a vote on
>
> MapGuide RFC 78 - Enhance transaction capability to Feature Service
> http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78
>
> Summary of review:
>
> What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?  Does the user need to rollback transaction within exception handling, or is this done automatically?
>  
>>>> No action taken.  To give flexibility, the user can do a Rollback in the exception handler.
>>>>        
>
> In case that FDO provider doesn't support transaction, it throws exception?
>  
>>>> RFC updated: if a provider doesn't support transaction, BeginTransaction() will throw an MgInvalidOperationException saying transaction is not supported.
>>>>        
>  
> I think too that it doesn't have to do auto roll back but another question comes to me. I assume that MgTransaction will get hold on one particular FDO connection until either Rollback or Commit is executed ?
>  
>>>> Yes, MgTransaction will hold on the particular FDO connection until Commit or Rollback is executed. And there is also a timeout for transaction that if it's not committed or rollbacked within the timeout, the server will automatically rollback the transaction as mentioned in the RFC.  
>>>>        
>
> Add a UpdateFeatures that uses transaction:
>  
>>>> Description added.
>>>>        
>
> +1 Tom
>
> Thanks
> Tom
> _______________________________________________
> mapguide-internals mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>  

_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Bruce Dechant]

+1 Bruce

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Tom Fukushima
Sent: Monday, July 27, 2009 9:55 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 78

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?  Does the user need to rollback transaction within exception handling, or is this done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in the exception handler.

In case that FDO provider doesn't support transaction, it throws exception?
>>> RFC updated: if a provider doesn't support transaction, BeginTransaction() will throw an MgInvalidOperationException saying transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another question comes to me. I assume that MgTransaction will get hold on one particular FDO connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until Commit or Rollback is executed. And there is also a timeout for transaction that if it's not committed or rollbacked within the timeout, the server will automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals

[Tom Fukushima]

RFC 78 has been adopted.

Thanks
Tom

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Tom Fukushima
Sent: Monday, July 27, 2009 9:55 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Motion: vote MapGuide RFC 78

Hi,

I motion for a vote on

MapGuide RFC 78 - Enhance transaction capability to Feature Service
http://trac.osgeo.org/mapguide/wiki/MapGuideRfc78

Summary of review:

What happens when one of ExecuteSqlQuery or ExecuteSqlNonQuery fails?  Does the user need to rollback transaction within exception handling, or is this done automatically?
>>> No action taken.  To give flexibility, the user can do a Rollback in the exception handler.

In case that FDO provider doesn't support transaction, it throws exception?
>>> RFC updated: if a provider doesn't support transaction, BeginTransaction() will throw an MgInvalidOperationException saying transaction is not supported.
 
I think too that it doesn't have to do auto roll back but another question comes to me. I assume that MgTransaction will get hold on one particular FDO connection until either Rollback or Commit is executed ?
>>> Yes, MgTransaction will hold on the particular FDO connection until Commit or Rollback is executed. And there is also a timeout for transaction that if it's not committed or rollbacked within the timeout, the server will automatically rollback the transaction as mentioned in the RFC.  

Add a UpdateFeatures that uses transaction:
>>> Description added.

+1 Tom

Thanks
Tom
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/mapguide-internals