developer.jelix.org is not used any more and exists only for history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Opened 13 years ago

Closed 13 years ago

#266 closed bug (fixed)

jDb: no support of different drivers on a same database type

Reported by: laurentj Owned by:
Priority: low Milestone: Jelix 1.0 RC1
Component: jelix:db Version: 1.0 beta2.1
Severity: major Keywords:
Cc: Blocked By:
Blocking: Documentation needed:
Hosting Provider: Php version:

Description

We couldn't create a driver for jDb which works on a same database of an existing driver. It causes bug in jDao because the driver name is used as the name of a database "type". For example, we couldn't create a special driver for postgresql, called "pgspecial" : jDao generates SQL queries for postgresql only if the driver name is "postgresql". So queries generated for the "pgspecial" driver are bad and not "postgresql" oriented.

Change History (2)

comment:1 Changed 13 years ago by laurentj

  • Milestone changed from Jelix 1.0beta3 to Jelix 1.3
  • Priority changed from high to low

I don't find a good solution for this ticket. The only one information we have for the compiler is the driver name. To have the database type, we have to load the db driver. But we can't since we don't know from which profil we should load the driver.

The only solution is to make work on ticket #101.

comment:2 Changed 13 years ago by laurentj

  • Milestone changed from Jelix 1.3 to Jelix 1.0
  • Resolution set to fixed
  • Status changed from new to closed

Since the ticket #101 is fixed, you can create a dao driver which inherits from the postgresql one's.

Fixed then.

Note: See TracTickets for help on using tickets.