1. 09 Dec, 2015 1 commit
    • Julien Cristau's avatar
      Backout "[entity,storage] remove hackish code from the bfss path · dc572d116731
      Julien Cristau authored
      The merge of the repo-side and web-side entity caches doesn't actually work,
      because entities have a _cw attribute which is sometimes a connection and
      sometimes a web request, and whose nature changes not-really-predictably
      whenever ResultSet.get_entity() is called and brings it out of the cache.
      
      This reverts commit 59a79300f213.
      dc572d116731
  2. 05 Oct, 2015 1 commit
  3. 29 Sep, 2015 1 commit
  4. 08 Sep, 2015 1 commit
  5. 09 Dec, 2015 1 commit
  6. 30 Nov, 2015 1 commit
  7. 07 Oct, 2015 1 commit
  8. 02 Sep, 2015 1 commit
  9. 25 Aug, 2015 1 commit
  10. 21 Aug, 2015 1 commit
  11. 22 Sep, 2015 1 commit
    • Sylvain Thénault's avatar
      fix bad-caching of datetime with tz info at sql generation time · cfded6d0da11
      Sylvain Thénault authored
      There is a special handling for datetime with tzinfo, where value was stored in
      the query cache. The implementation of merge_args was simply overwriting
      parameters of the query with those in the query cache, expecting no collision.
      
      To fix this:
      * handle replacement of tzinfo in merge_args, not at sql generation time
      * add an assertion to ensure we've actually no collision
      
      Closes #6978316
      cfded6d0da11
  12. 29 Sep, 2015 3 commits
  13. 24 Jul, 2015 2 commits
  14. 06 Aug, 2015 2 commits
  15. 25 Aug, 2015 1 commit
  16. 28 Jul, 2015 2 commits
    • Julien Cristau's avatar
      [server] typo fix · d8df2c7cff1a
      Julien Cristau authored
      d8df2c7cff1a
    • Julien Cristau's avatar
      Fix (de)serialization of ComputedRelation read permissions · 1d824df4f2bd
      Julien Cristau authored
      For normal relation types, permissions don't need to be stored since
      they're just default values for the relation definitions.  However,
      computed relations are serialized (as CWComputedRType), while their
      relation definitions are added at schema finalization time, and are only
      in memory.  So add the 'read_permission' relation to CWComputedRType,
      and the appropriate hooks to save and restore those permissions.
      
      To avoid having to touch yams, we drop the 'add' and 'delete'
      permissions from the default computed relation permissions; this should
      probably be backported there.  The actual permissions (set on the
      relation definitions) are hardcoded in finalize_computed_relations
      anyway.
      
      In deserialize_schema, the CWComputedRType handling needs to be delayed
      a little bit, until after we've called deserialize_ertype_permissions.
      
      The rql2sql test is adjusted because CWComputedRType has a 'name'
      attribute and the 'read_permission' relation, which generates ambiguity
      vs CWEType.
      
      We add an explicit CubicWebRelationSchema.check_permission_definitions,
      since we need to check both that computed and non-computed rtypes are
      defined properly.
      
      Based on report and initial patch from Christophe de Vienne (thanks!).
      
      Closes #5706307
      1d824df4f2bd
  17. 22 Jul, 2015 1 commit
  18. 27 Jul, 2015 1 commit
  19. 20 Jul, 2015 3 commits
  20. 10 Jul, 2015 1 commit
  21. 07 Jul, 2015 3 commits
  22. 25 Nov, 2015 1 commit
  23. 24 Sep, 2015 1 commit
    • Sylvain Thénault's avatar
      [migration] don't handle data deletion anymore on schema changes · 977def81780a
      Sylvain Thénault authored
      In most cases when we want to drop some entity/relation type, we don't care
      whether hooks are called on their deletion. There is even low chances that some
      hooks still exists, based on an old version of the schema. Last but not least,
      this is horribly inefficient.
      
      So this should be clearly documented and handled by application's programmer if
      desired.
      
      This patch removes unnecessary deletion (because table or column will be later
      dropped) and reimplements the case of partial deletion (only one relation
      definition among several, hence the database structure isn't modified) using
      sql.
      
      Only one test regarding deletion of inlined relation def is added as other cases
      seem to be covered by existing tests.
      
      Closes #7023315
      977def81780a
  24. 24 Nov, 2015 3 commits
  25. 30 Jun, 2015 1 commit
    • Sylvain Thénault's avatar
      [repository] deprecate the extid2eid based multi-sources API · fed8bd56f223
      Sylvain Thénault authored
      This API is cumbersome and lead to obfuscated code because of the callback
      mecanism implied when some entity has to be created.
      
      Since we dropped the "true" multi-source, this mecanism is not needed anymore
      and one should prefer to use the dataimport API inside its parser instead.
      
      Notice the cwxml parser will trigger the deprecation warning, it should not be
      used anymore in favor of ad-hoc parsers.
      fed8bd56f223
  26. 23 Nov, 2015 1 commit
  27. 24 Nov, 2015 1 commit
    • Sylvain Thénault's avatar
      [ldapfeed / dataimport] port ldapfeed parser to dataimport API · addc7ba36f69
      Sylvain Thénault authored
      This makes the code easier to understand and will allow to deprecate the old
      multi-sources api, based on creation callback through repo.extid2eid.
      
      Currently with this patch, modification dates are not checked, hence
      entities will be systematically updated.
      
      We run the import with no hooks, because RQLObjectStore can only add
      entities to the system source.
      addc7ba36f69
  28. 23 Nov, 2015 1 commit
  29. 24 Nov, 2015 1 commit