database

KarenS has kicked off a discussion on CCK field structure for core in D7. It's also webchick's itch of the week.

David Strauss is already commenting, and has experience in RDF from the Internet Archive, but it would be good to have other experienced people giving this the once over. Since these fields are likely to be a major way that people "transparently" create subject/predicate/object relationships, we better get this right (and performant, working on shared hosts, etc. etc.).

Tôi tìm được bài viết này, rất mừng
http://drupal.org/node/18429
Nhưng tới đoạn: "This only works with two databases of the same type"

Có cách nào để sử dụng cùng lúc MySQL và Oracle không?

I installed phpbb module. (drupal 5.3 and phpbb3)
If I change a password in phpbb profile, it doesn't works in drupal.
if drupal admin deletes a user in drupal, that user doesn't work any longer, because I have to log from drupal; but if I try to create again that username, it says

My primary battle plan should be enhance Drupal cross database compatibility. I have involved in this topic for around a year, and I would like to keep it on going. To accomplish this target, I would like to complete the following tasks before D7 code freeze:

<

ul>

I have summarize most of my personal battle targets in here. Most logic are proved as functioning, and they are all get set for the open of D7 public development. On the other hand, I would like to explore if this may integrate with other interest musings with Data API, so we will able get all stuff better in D7 ;-)

I have been pondering the question of a data API for a while, as have a lot of people. Much of the recent discussion has focused on an Active Record approach to a data API. Now, Active Record is a very powerful architectural pattern. It maps nicely from storage to interface, it can be fairly self-documenting, and it is conceptually simple and approachable.

It is also, I believe, insufficient.

As a site goes live and we do performance tweaking and benchmarking one of the common results is adding database indexes. I post this into the CCK group since one of the common sources of slow queries is for queries against the CCK tables. For example, a site that has a block that queries a field table to look for information about that field for every page load can quickly make its way into the slow query log. Adding an index to the field is likely to be the best solution.

Hi Everybody,

I am totally new to the drupal world and so I am going to ask what I am sure is a total noob question.

I am developing a product that offers storage in the internet cloud via a rest API.

I would like to offer mod or a plugin that would allow drupal data to be pulled from a non-standard source, i.e. my database system. How easy/hard is this? Are there bottleneck routines in drupal that "get and set" the data so that these functions could be replaced or overridden and be using a different source?

Hi all,
i'm a phpbb and drupal user but there is a thing that i dont like
and that is changing a database table in a live site.. i did it on my live site and my user count was going from 100 to 1000 but there are only 100 so the next user has gotten ID 1001 and i dont like when that hapens :P.

this is what arkepp sayed:

"It is not changing the database, it is changing a value in the sequence table. It is the equivalent of a spammer visiting your site, adding 100 (or 1000, as I recommend, but the value is of no importance) users and then you deleting them again.

Once foreign keys are specified during table creation, we will have to make sure to create tables in the correct order. e.g. You can't create system.schema, whose files table has a uid column, before you create user.schema which creates the users table which hold the master uid column.

If this proves too difficult we can use ALTER TABLE to put the foreign key contraints in afterward, but that seems much less desireable.