Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I added a date field to "Basic Page" content type, but I cannot save when adding content. I am using Oracle 11g Express Edition.
Comments
Comment #1
KarenS CreditAttribution: KarenS commentedIt has not been tested at all with Oracle. Someone who knows Oracle would have to provide a patch to make the necessary changes to date_api_sql.inc in the Date API module, following the same pattern that was used for other database engines.
Comment #2
KarenS CreditAttribution: KarenS commentedComment #3
Dhiego Carvalho Santos CreditAttribution: Dhiego Carvalho Santos commentedtested on ORACLE and still does not work, it is still something changed?
Comment #4
GilbertoSantiz CreditAttribution: GilbertoSantiz commentedYo tengo el mismo problema, no hay solución aún?
I have the same problem, no solution yet?
Comment #5
jjjaroscak CreditAttribution: jjjaroscak commentedThe README.txt file says "The SQL functions are found in date_api_sql.inc, which is not included by default. Include that file if you want to use these functions:" but I have no idea where to include it to. So if I attempt at getting this to work where do I include the file? Is it just this file we need to edit to get it to work with Oracle?
Comment #6
faith45 CreditAttribution: faith45 commentedWhat is the resolution to this issue? We encountered the same problem.
Comment #7
abendanio9 CreditAttribution: abendanio9 commentedI saw date_api_sql.inc and it was included at date.module.
Does anyone knows the solution?
Comment #8
abendanio9 CreditAttribution: abendanio9 commentedgot the answer for oracle...
use the drupal admin... manage field and change the field type of the date into unix_timestamp or ISO
thant's it!.. hope it will help
Comment #9
abendanio9 CreditAttribution: abendanio9 commentedgot the answer for oracle...
use the drupal admin... manage field and change the field type of the date into unix_timestamp or ISO
that's it!.. hope it will help
Comment #10
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedContextual filters with date are not supported. The date_api_sql.inc file states a todo feature for oracle support, together with a coworker, we created the patch in attachment with the required date/ time cases for oracle db_type.
Development setup is
Requesting review on this patch to be included in future releases of the date module, thanks.
Comment #12
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedComment #15
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedI have skiped a step (switch to my local branch) when creating the patch, I'm going trough the patch to resubmit.
Comment #16
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedResubmit patch for retest
Comment #17
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedComment #18
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedComment #19
ricardoj.m.pinto@gmail.com CreditAttribution: ricardoj.m.pinto@gmail.com commentedComment #21
René-Marc Simard CreditAttribution: René-Marc Simard commented@ricardojmartins
I had a client on Oracle 11g last year and also had to write custom code to support the Date module. Our solutions are very similar! :-) I cannot test it (nor yours) anymore as the project finally migrated to MySQL, but maybe that bit of code could help out. Take what you want from it!
Comment #22
Valentine94Bot
Comment #24
hass CreditAttribution: hass commentedComment #25
metallized CreditAttribution: metallized commentedHi i want to declare this affect the user registration process if exists a custom date field using the format "date" it can be fixed setting the format to "date unix".
The error on registration process is:
DatabaseTransactionNoActiveException: in DatabaseConnection->rollback() (line 1038 of /var/www/html/includes/database/database.inc).
I trace the error to the function user_save when call field_attach_insert.