1 Reply by Fabion

(4 replies, posted in General)

9  down vote accepted
   

If you want to store a pickled object, you'll need to use a blob, since it is binary data. However, you can, say, base64 encode the pickled object to get a string that can be stored in a text field.

Generally, though, doing this sort of thing is indicative of bad design, since you're storing opaque data you lose the ability to use SQL to do any useful manipulation on that data. Although without knowing what you're actually doing, I can't really make a moral call on it.

Go to forum: General

2 Reply by Fabion

(4 replies, posted in Miscalleneous posts)

1  down vote
   

I'd take a slightly different approach to this problem. I'd set up components for your Core Runtime and for each project/product specific part, but don't make these components branch specific. So, you might have the following components in your Jira project:

    * Core
    * ProductX
    * ProductY
    * ProductZ

Then, I'd differentiate the different branches by version. I'm assuming that you have some type of version numbering system that allows you to tie your binaries in the field back to a particular branch and version. Set up a version in Jira for each version/branch. When you report issues into Jira, you can select one or more affected versions.

This system has a couple of advantages:

   1. If an issue spans multiple versions/branches you can identify all of the affected versions in the issue.
   2. You can set the Fix For Version to one or more versions. At times, you may only fix an issue in your trunk, or a certain branch. Perhaps it's a major issue and you have to port the fix across branches. This system gives you the flexibility to see all of that and report on it.

Go to forum: Miscalleneous posts

3 Reply by Fabion

(3 replies, posted in General)

I also have same problem with table but now solved......Thanks lucky .

Go to forum: General