Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oracle AQ EnqueueTime not correctly available #446

Open
Leonardo-Ferreira opened this issue Mar 21, 2025 · 5 comments
Open

Oracle AQ EnqueueTime not correctly available #446

Leonardo-Ferreira opened this issue Mar 21, 2025 · 5 comments

Comments

@Leonardo-Ferreira
Copy link

I'm dequeuing messages from my oracle AQ but the property "EnqueueTime" does not have the milliseconds portion of it! How can I retrieve it?

@alexkeh
Copy link
Member

alexkeh commented Mar 21, 2025

EnqueueTime returns a DateTime type. It should include a placeholder for milliseconds. Is the issue that the milliseconds placeholder contains just zeros?

Is this question about unmanaged, managed, or core ODP.NET? Which ODP.NET version?

@Leonardo-Ferreira
Copy link
Author

Leonardo-Ferreira commented Mar 24, 2025

Hello @alexkeh, thanks for the interest.

The issue is that the milliseconds part is always zero.

I'm using Oracle.ManagedDataAccess.Core v23.7.0

@alexkeh
Copy link
Member

alexkeh commented Mar 24, 2025

The ODP.NET dev team did some more research into this question. The DB AQ enqueue time granularity is in seconds only. Thus, ODP.NET cannot provide the millisecond information since the DB doesn't provide it.

Once the DB provides millisecond data, ODP.NET AQ should act as a passthrough and be able to return it.

@Leonardo-Ferreira
Copy link
Author

@alexkeh
Copy link
Member

alexkeh commented Mar 28, 2025

@Leonardo-Ferreira
I see. ODP.NET supports the ENQ_TIME, but not the ENQ_TIMESTAMP. I've filed ER 37767276 to track this request. ODP.NET would probably provide a second enqueue time property for the millisecond granularity.

Can you provide a short business case on the need and urgency for the feature? I'll add the info to the ER.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants