On Jun 27, 2009, at 9:57 PM, Harmeet Bedi wrote:
Regd: 'Doing an automated migration would only work if you know that
all
current values in the database are among the enumerated options you
want to
migrate to'
Migration could check and create the enumerated option if it does
not exist.
How do you handle live changes to systems with multiple applications
servers?
-David
On Jun 27, 2009, at 10:02 PM, Adam Heath wrote:
Al Byers wrote:
Ean,
Could you please give a little more information about the type of
content
and merges that you see in practice, so I can see if the
How would this be better than the current practices? These are
described here:
http://docs.ofbiz.org/display/OFBTECH/Revisions+Requiring+Data+Migration
and here:
http://docs.ofbiz.org/display/OFBTECH/General+Entity+Overview ->
Deprecated Entities
-David
On Jun 27, 2009, at 10:58 PM, H
How about this proposal
1. Add enumeration id in addition to text field for these and any other
places where text could be replaced with reference. Some locations
(a) add Person::salutationTypeId references
PersonSalutionType:salutationTypeId
(b) add Person:personalTitleTypeId references
Person
Al Byers wrote:
> Ean,
>
> Could you please give a little more information about the type of content
> and merges that you see in practice, so I can see if the CMS could be built
> out to handle them?
Actually, storing these things in the database is not the best way to
go. It keeps people from
Regd: 'Doing an automated migration would only work if you know that all
current values in the database are among the enumerated options you want to
migrate to'
Migration could check and create the enumerated option if it does not exist.
So Party has refrences to PersonalTitleId, where PersonalT
Yeah, that's the exact issue with the title too... there are
potentially thousands of them if you try to include every culture in
the world (and hundreds even for English speaking cultures, especially
if you include royalty/class titles, military titles, etc). On the
other hand, now that
I would say yes - but it does limit us to what we know about - but
that's the case with any lookup.
Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Jun 27, 2009, at 11:32 AM, David E Jones wrote:
On Jun 27, 2009, at 8:07 AM, Jacopo Cappel
On Jun 27, 2009, at 8:07 AM, Jacopo Cappellato wrote:
On a side note, would you want to do this with the suffix or any
other fields?
I am sorry but I don't understand the above question.
The questions was mainly for Bob, but I guess something for anyone to
consider: would we want to ha
[
https://issues.apache.org/jira/browse/OFBIZ-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brajesh Patel updated OFBIZ-2667:
-
Attachment: CSV_and_PDF_view_OFBIZ-2667.patch
Here I have attached patch for export search result
[
https://issues.apache.org/jira/browse/OFBIZ-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brajesh Patel updated OFBIZ-2667:
-
Component/s: accounting
Fix Version/s: SVN trunk
Description:
Now allow u
Add C
-
Key: OFBIZ-2667
URL: https://issues.apache.org/jira/browse/OFBIZ-2667
Project: OFBiz
Issue Type: Sub-task
Reporter: Brajesh Patel
1.
https://localhost:8443/accounting/control/FindAcctgTrans?organizationPartyId=Comp
Show a larger portlet screenshot
Key: OFBIZ-2666
URL: https://issues.apache.org/jira/browse/OFBIZ-2666
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects Versions: SVN trunk
[
https://issues.apache.org/jira/browse/OFBIZ-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Busco updated OFBIZ-2666:
---
Attachment: LargerPortletScreenshots.patch
> Show a larger portlet screenshot
> -
[
https://issues.apache.org/jira/browse/OFBIZ-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724861#action_12724861
]
BJ Freeman commented on OFBIZ-2657:
---
OK
in my implementatiion I use Company as the defual
Add Csv and PDF generation functionalities to reporting type screens of
Accounting components.
--
Key: OFBIZ-2665
URL: https://issues.apache.org/jira/browse/OFBIZ-2665
[
https://issues.apache.org/jira/browse/OFBIZ-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-2664.
--
Resolution: Fixed
Thanks Chirag!
Done at r788976.
--
Ashish Vijaywargiya
> Portlet to
Hi David,
On Jun 27, 2009, at 1:42 AM, David E Jones wrote:
This is a tough one since you would be moving from a less
constrained field to a more constrained one, ie a free-form field to
a field with an enumerated set of options. Doing an automated
migration would only work if you know t
Thanks Hans for quick solution.
Regards
--
Divesh
Hans Bakker wrote:
should be ok now
On Sat, 2009-06-27 at 17:52 +0530, Divesh Dutta wrote:
Hi Rishi,
Hans can do a quick fix. I can tell you the problem, i.e indexing is
applied to "infoName" field of NoteData entity. And such field d
should be ok now
On Sat, 2009-06-27 at 17:52 +0530, Divesh Dutta wrote:
> Hi Rishi,
>
> Hans can do a quick fix. I can tell you the problem, i.e indexing is
> applied to "infoName" field of NoteData entity. And such field does not
> exist. May be Hans wanted to apply indexing on "noteInfo".
Hi Rishi,
Hans can do a quick fix. I can tell you the problem, i.e indexing is
applied to "infoName" field of NoteData entity. And such field does not
exist. May be Hans wanted to apply indexing on "noteInfo". Lets see What
Hans says.
Thanks
--
Divesh
Rishi Solanki wrote:
Steps to reprodu
Steps to reproduce :
I tried derby database for installing ofbiz on trunk revision 788950 and
then ran command "ant clean-all && ant run-install".
I observed following error (Same error coming for external db i.e postgres):
[java] 2009-06-27 17:18:27,489 (main) [ DatabaseUtil.java:2754:INFO
FYI - this may be the same issue I reported (OFBiz-2596). Problem with
CSS layout and elements not sizing (height & width) as you would expect.
Ruth
Sumit Pandit (JIRA) wrote:
[ https://issues.apache.org/jira/browse/OFBIZ-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabp
[
https://issues.apache.org/jira/browse/OFBIZ-2655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya closed OFBIZ-2655.
--
Resolution: Fixed
Thanks Chirag.
Done at r788945.
--
Ashish Vijaywargiya
> Portlet to
[
https://issues.apache.org/jira/browse/OFBIZ-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Vijaywargiya reassigned OFBIZ-2664:
--
Assignee: Ashish Vijaywargiya
> Portlet to show best selling products of the da
Portlet to show best selling products of the day
Key: OFBIZ-2664
URL: https://issues.apache.org/jira/browse/OFBIZ-2664
Project: OFBiz
Issue Type: New Feature
Components: product
[
https://issues.apache.org/jira/browse/OFBIZ-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chirag Manocha updated OFBIZ-2664:
--
Attachment: BestSellingProduct_OFBiz-2664.patch
Here is the patch for the same.
> Portlet to s
[
https://issues.apache.org/jira/browse/OFBIZ-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Mouawad updated OFBIZ-2599:
Attachment: memory.png
Memory image of Production server.
4 days of run.
Around the point
[
https://issues.apache.org/jira/browse/OFBIZ-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Mouawad closed OFBIZ-2636.
---
Resolution: Invalid
> Performance ISSUE in ModelServiceReader due to Too Coarse synchronizati
Difficult to find. It was enteries -> entries.
--
Ashish
On Sat, Jun 27, 2009 at 1:26 PM, wrote:
> Author: ashish
> Date: Sat Jun 27 07:56:29 2009
> New Revision: 788936
>
> URL: http://svn.apache.org/viewvc?rev=788936&view=rev
> Log:
> Fixed Typo.
>
> Modified:
>ofbiz/trunk/applications/ac
[
https://issues.apache.org/jira/browse/OFBIZ-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724818#action_12724818
]
Akash Jain commented on OFBIZ-2663:
---
Thanks Vikas :)
Thanks and Regards
--
Akash Jain
On Jun 26, 2009, at 4:43 PM, Bob Morley wrote:
Basically what Jacopo has indicated here is exactly what our
requirements
were. When products come in they may have had a "basic receive"
completed;
but they have not been moved to a salable location. Moreover, we
actually
had two stores i
[
https://issues.apache.org/jira/browse/OFBIZ-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724817#action_12724817
]
Sumit Pandit commented on OFBIZ-2662:
-
Thank you Ashish for your comments in commit not
[
https://issues.apache.org/jira/browse/OFBIZ-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724816#action_12724816
]
Sumit Pandit commented on OFBIZ-2611:
-
Thank you Ashish And Jacopo for your commit.
>
This is a tough one since you would be moving from a less constrained
field to a more constrained one, ie a free-form field to a field with
an enumerated set of options. Doing an automated migration would only
work if you know that all current values in the database are among the
enumerat
35 matches
Mail list logo
