Deprecated - Drupal core

Hi all,
I understand you're removing supporto for POSTGRESQL in 4.4, so I understand you will support only MySQL.
I was wondering if you're going to support native functionalities of MYSQL that could simplify Drupal development.
I'm thinking of:
- Autoincrement fields, that could avoid using and maintaining sequences
- FULLTEXT indexing, that could provide native support of fulltext search, avoiding creation and update of search_index table

Hello,

I'm trying to extend the security system to allow users to edit any static page that they have created by not the pages of others. Currently there is only the "maintain static page" access right, which does not do what I want.

I managed to get the "Administer" link under every page that the user created (but not under ones which others have created) by hacking node.module's node_link() method. I added a check like this:

Hello. I don't know where I could post a feature request, but I had this idea and I found it would be a great addition to Drupal. I would like to see new attributes for taxonomy terms and vocabularies that would allow a taxonomy to define the language for the site or the theme currently displaying. For instance, in a vocabulary named "Language", a term called "Portuguese" would change locale to Portuguese and, possibly, the theme.

I'd like to hack the sidebar output so that certain blocks aren't output if a user isn't logged in. I know that the path can be set to define when blocks are displayed based on the URL path ... But I want this type behavior based on logged in/not logged in.

Any ideas where I'd start hacking, and how hard this might be? I'd like to do this in a Theme independant fashion.

When showing trimmed version of article, HTML appears to be break. Actually, unclosed <table> breaks design absolutly. Maybe it's possible to do more intelligent cutoff? At list show all the content up to </table> tag.

Hi aLL,

We are running some drupal based web community sites here in Brazil intended to be used by social organizations. Drupal is really a great software, thanx.

At this moment we are using postgresql as database for drupal and we are going to some troubleshooting with this. Most common dificults we had till now were easy to overcome so we would be very happy to help people having problems. Despite this I think drupal use with postgresql could be very improved if we have good answers for questions posted to this forum. For example purposes only:

# warning: pg_exec() query failed: ERROR: pg_atoi: zero-length string ( specific postgresql >= 7.3)
example: http://drupal.org/node/view/2568

# mysql specific LIMIT clause
example: http://drupal.org/node/view/2551

# drupal setup with postgresql
example: http://drupal.org/node/view/2460

# postgresql request for support
example: http://drupal.org/node/view/5473

# encoding postgres related
example: http://drupal.org/node/view/4781

Are there instructions to drupal development with postgresql we could use to start a plan to resolve problems like above and integrate solutions to drupal releases and modules releases? In fact, if community thinks it is usefull for drupal we really like to help.

In meantime we started this week some efforts to modify (or create) drupal database schema mainly for modules development for postgresql 7.3.x to become it more suitable for fresh instalations. Starting point is ERD diagram ( http://drupal.org/book/view/1805 ). We note in example that NOT NULL constraints at every column in database schema is a problem to postgresql porting, are we correct?